Skip to content

LIEF vulnerable to heap based buffer overflow via print_binary function

High severity GitHub Reviewed Published Sep 14, 2022 to the GitHub Advisory Database • Updated Jan 29, 2023

Package

pip lief (pip)

Affected versions

>= 0, <= 0.12.1

Patched versions

None

Description

LIEF commit 365a16a was discovered to contain a heap-buffer overflow via the function print_binary at /c/macho_reader.c. Commit 0033b6312fd311b2e45e379c04a83d77c1e58578 contains a patch.

References

Published by the National Vulnerability Database Sep 13, 2022
Published to the GitHub Advisory Database Sep 14, 2022
Reviewed Sep 20, 2022
Last updated Jan 29, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.081%
(36th percentile)

Weaknesses

CVE ID

CVE-2022-38495

GHSA ID

GHSA-42vg-2q93-fj6j

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.