CVE-2024-22653

Exp

yasm commit 9defefae was discovered to contain a NULL pointer dereference via the yasm_section_bcs_append function at section.c.

Published: 2025-05-29 Last update: 2025-06-18 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-22653 is rated Exploit Available (50/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.22%). 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-22653

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

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

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 2026-03-25 0.07% 0.22% +0.16%
2 2026-02-12 0.04% 0.07% +0.02%
3 2025-11-21 — 0.04% —

Full EPSS history (7 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
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.
 2.2 2.5 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-22653

OS Trackers for CVE-2024-22653

vendor priority summary link
debian unimportant CVE-2024-22653 unimportant priority: Debian including 1 source packages (yasm), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2024-22653
redhat medium — https://access.redhat.com/security/cve/CVE-2024-22653
suse low CVE-2024-22653 severity low: SUSE including 2 source package names (yasm, yasm-devel), 34 product×package rows across 18 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (18 product lines)): Will Not Fix 34. https://www.suse.com/security/cve/CVE-2024-22653/
ubuntu medium CVE-2024-22653 medium priority: Ubuntu including 1 source packages (yasm), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): needs-triage 7, ignored 2. https://ubuntu.com/security/CVE-2024-22653

Affected software / configurations for CVE-2024-22653

Vendor Product Version Raw CPE
yasm_project yasm 2023-09-22 cpe:2.3:a:yasm_project:yasm:2023-09-22:*:*:*:*:*:*:*

References for CVE-2024-22653

cvelogic Threat Intelligence