What is the CVSS score of CVE-2019-12788?

CVE-2019-12788 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 4.5%.

Is there a public PoC exploit available for CVE-2019-12788?

Yes, a public proof-of-concept exploit is available for CVE-2019-12788. Prioritise patching immediately. EPSS: 4.5%.

Proshow Producer CVE-2019-12788

HIGH

Out-of-bounds Write (CWE-787)

2019-06-10 cve@mitre.org

Buffer Overflow Memory Corruption Proshow Producer

7.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.8 HIGH

AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Jun 10, 2019 - 19:29 nvd

HIGH 7.8

DescriptionNVD

An issue was discovered in Photodex ProShow Producer v9.0.3797 (an application that runs with Administrator privileges). It is possible to perform a buffer overflow via a crafted file.

AnalysisAI

An issue was discovered in Photodex ProShow Producer v9.0.3797 (an application that runs with Administrator privileges). Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Out-of-bounds Write (CWE-787), which allows attackers to write data beyond allocated buffer boundaries leading to code execution or crashes. An issue was discovered in Photodex ProShow Producer v9.0.3797 (an application that runs with Administrator privileges). It is possible to perform a buffer overflow via a crafted file. Affected products include: Photodex Proshow Producer.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Validate write boundaries, use memory-safe languages, enable compiler protections (ASLR, stack canaries).