CVE-2024-31636

Exp

An issue in LIEF v.0.14.1 allows a local attacker to obtain sensitive information via the name parameter of the machd_reader.c component.

Published: 2024-05-03 Last update: 2025-08-21 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-31636 is rated Exploit Available (50/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.08%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-31636

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-31636

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-06-11 0.03% 0.08% +0.04%
2 2025-04-15 0.06% 0.03% -0.02%
3 2025-03-17 — 0.06% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-31636

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.9 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 1.3 2.5 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-31636

GitHub Security Advisory for CVE-2024-31636

GHSA-377p-g8gr-5wpg · Severity: low · Ecosystem: pip — LIEF obtain sensitive information via the name parameter

OS Trackers for CVE-2024-31636

vendor priority summary link
debian not yet assigned CVE-2024-31636 not yet assigned priority: Debian including 1 source packages (lief), 2 status rows across 2 suites (bookworm, bullseye): open 2. https://security-tracker.debian.org/tracker/CVE-2024-31636
ubuntu medium CVE-2024-31636 medium priority: Ubuntu including 1 source packages (lief), 8 status rows across 8 suites (focal, jammy, mantic, noble, oracular, plucky, questing, upstream): DNE 4, needs-triage 3, ignored 1. https://ubuntu.com/security/CVE-2024-31636

Affected software / configurations for CVE-2024-31636

Vendor Product Version Raw CPE
lief-project lief 0.14.1 cpe:2.3:a:lief-project:lief:0.14.1:*:*:*:*:*:*:*

References for CVE-2024-31636

cvelogic Threat Intelligence