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

CVE-2022-28044 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 1.9%.

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

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

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

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

Irzip CVE-2022-28044

CRITICAL

Out-of-bounds Write (CWE-787)

2022-04-15 cve@mitre.org

Memory Corruption Buffer Overflow Irzip Debian Linux

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Apr 15, 2022 - 14:15 nvd

CRITICAL 9.8

DescriptionNVD

Irzip v0.640 was discovered to contain a heap memory corruption via the component lrzip.c:initialise_control.

AnalysisAI

Irzip v0.640 was discovered to contain a heap memory corruption via the component lrzip.c:initialise_control. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, 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. Irzip v0.640 was discovered to contain a heap memory corruption via the component lrzip.c:initialise_control. Affected products include: Irzip Project Irzip, Debian Debian Linux.

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).