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

CVE-2022-0367 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: 0.4%.

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

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

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

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

Libmodbus CVE-2022-0367

HIGH

Buffer Overflow (CWE-119)

2022-08-29 secalert@redhat.com

Buffer Overflow Libmodbus Extra Packages For Enterprise Linux Fedora Debian Linux

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

Aug 29, 2022 - 15:15 nvd

HIGH 7.8

DescriptionNVD

A heap-based buffer overflow flaw was found in libmodbus in function modbus_reply() in src/modbus.c.

AnalysisAI

A heap-based buffer overflow flaw was found in libmodbus in function modbus_reply() in src/modbus.c. Rated high severity (CVSS 7.8), this vulnerability is no authentication required, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Buffer Overflow (CWE-119), which allows attackers to corrupt memory to execute arbitrary code or crash the application. A heap-based buffer overflow flaw was found in libmodbus in function modbus_reply() in src/modbus.c. Affected products include: Libmodbus, Fedoraproject Extra Packages For Enterprise Linux, Fedoraproject Fedora, Debian Debian Linux.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.