CVE-2020-37162
Unknown Unknown - Not Provided
Buffer Overflow in Wedding Slideshow Studio 1.36 Enables Code Execution

Publication date: 2026-02-07

Last updated on: 2026-02-24

Assigner: VulnCheck

Description
Wedding Slideshow Studio 1.36 contains a buffer overflow vulnerability in the registration key input that allows attackers to execute arbitrary code by overwriting memory. Attackers can craft a malicious payload of 1608 bytes to trigger a stack-based buffer overflow and execute commands through the registration key field.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-07
Last Modified
2026-02-24
Generated
2026-05-27
AI Q&A
2026-02-07
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
wedding-slideshow-studio wedding_slideshow_studio to 1.36 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-122 A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2020-37162 is a buffer overflow vulnerability in Wedding Slideshow Studio version 1.36. It occurs in the registration key input field where an attacker can supply a specially crafted payload of 1608 bytes. This causes a stack-based buffer overflow that overwrites memory, allowing the attacker to execute arbitrary code.

The vulnerability requires local access and user interaction, as the attacker must input the malicious registration key. The flaw exploits the lack of modern memory protections in a loaded DLL, enabling the execution of attacker-controlled commands.


How can this vulnerability impact me? :

This vulnerability can have severe impacts including unauthorized code execution on the affected system. An attacker who successfully exploits this flaw can run arbitrary commands, potentially leading to full system compromise.

  • Loss of confidentiality by accessing sensitive data.
  • Loss of integrity by modifying or corrupting data.
  • Loss of availability by disrupting normal operation of the software or system.

How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability is a local buffer overflow in the Wedding Slideshow Studio 1.36 application, specifically triggered by providing a specially crafted registration key input of 1608 bytes. Detection involves checking if the application is present and if the registration key input field has been supplied with unusually long or malformed data.

Since the exploit requires local user interaction and pasting a crafted payload into the registration key field, network detection is unlikely. Instead, detection can focus on monitoring the application usage and scanning for the presence of the vulnerable version (1.36 or earlier).

Suggested commands or steps to detect the vulnerability include:

  • Verify the installed version of Wedding Slideshow Studio to confirm if it is version 1.36 or earlier.
  • Use file integrity or hash checking tools on the executable to identify the vulnerable version.
  • Monitor application logs or user activity for attempts to input unusually long registration keys (around 1608 bytes).
  • On Windows, use tools like Process Monitor (ProcMon) to watch for abnormal behavior or crashes related to the registration key input.
  • No specific network commands or signatures are available due to the local and user-interactive nature of the exploit.

What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps for this vulnerability include:

  • Avoid using or running Wedding Slideshow Studio version 1.36 or earlier until a patch or update is available.
  • Do not enter or accept registration keys from untrusted sources, especially unusually long or suspicious inputs.
  • Restrict local user access to the application to trusted users only, minimizing the risk of malicious payload execution.
  • Monitor the system for crashes or abnormal behavior related to the application, which may indicate exploitation attempts.
  • If possible, apply application whitelisting or sandboxing to limit the impact of potential exploitation.
  • Contact the software vendor or check official sources for patches or updates addressing this vulnerability.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart