What is the CVSS score of CVE-2022-36752?

CVE-2022-36752 has a CVSS 3.1 base score of 5.5 (Medium). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H. EPSS exploitation probability: 0.4%.

Is there a public PoC exploit available for CVE-2022-36752?

Yes, a public proof-of-concept exploit is available for CVE-2022-36752. Prioritise patching immediately. EPSS: 0.4%.

Is there a patch available for CVE-2022-36752?

Yes, a patch is available for CVE-2022-36752. Update the affected software to the latest version immediately.

Png2Webp CVE-2022-36752

MEDIUM

Out-of-bounds Write (CWE-787)

2022-07-28 cve@mitre.org

Memory Corruption Buffer Overflow Png2Webp

5.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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:N/I:N/A:H

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

CVE Published

Jul 28, 2022 - 23:15 nvd

MEDIUM 5.5

DescriptionNVD

png2webp v1.0.4 was discovered to contain an out-of-bounds write via the function w2p. This vulnerability is exploitable via a crafted png file.

AnalysisAI

png2webp v1.0.4 was discovered to contain an out-of-bounds write via the function w2p. Rated medium severity (CVSS 5.5), this vulnerability is no authentication required, low attack complexity. Public exploit code 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. png2webp v1.0.4 was discovered to contain an out-of-bounds write via the function w2p. This vulnerability is exploitable via a crafted png file. Affected products include: Png2Webp Project Png2Webp.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate write boundaries, use memory-safe languages, enable compiler protections (ASLR, stack canaries).