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

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

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

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

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

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

Stb Image H CVE-2022-28042

HIGH

Use After Free (CWE-416)

2022-04-15 cve@mitre.org

Memory Corruption Use After Free Information Disclosure Stb Image H Fedora Debian Linux

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Apr 15, 2022 - 14:15 nvd

HIGH 8.8

DescriptionNVD

stb_image.h v2.27 was discovered to contain an heap-based use-after-free via the function stbi__jpeg_huff_decode.

AnalysisAI

stb_image.h v2.27 was discovered to contain an heap-based use-after-free via the function stbi__jpeg_huff_decode. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Use After Free (CWE-416), which allows attackers to access freed memory to execute arbitrary code or crash the application. stb_image.h v2.27 was discovered to contain an heap-based use-after-free via the function stbi__jpeg_huff_decode. Affected products include: Nothings Stb Image.H, Fedoraproject Fedora, Debian Debian Linux.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use smart pointers or garbage-collected languages. Set pointers to NULL after freeing. Enable memory sanitizers.