CVE-2024-40897

Stack-based buffer overflow vulnerability exists in orcparse.c of ORC versions prior to 0.4.39. If a developer is tricked to process a specially crafted file with the affected ORC compiler, an arbitrary code may be executed on the developer's build environment. This may lead to compromise of developer machines or CI build environments.

Published: 2024-07-26 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-40897 is rated Low Risk (32.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.06%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

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

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

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-12-15 0.04% 0.06% +0.01%
2 2025-11-21 0.07% 0.04% -0.03%
3 2025-11-18 0.07%

Full EPSS history (8 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.7 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H 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:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
0.8 5.9 [email protected]
7.0 3.1 HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H 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: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: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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.0 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-40897

OS Trackers for CVE-2024-40897

vendor priority summary link
alpine high CVE-2024-40897: 1 source package rows (orc); 7 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 7, open 0. https://security.alpinelinux.org/vuln/CVE-2024-40897
debian not yet assigned CVE-2024-40897 not yet assigned priority: Debian including 1 source packages (orc), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2024-40897
gentoo high CVE-2024-40897: 1 GLSA(s) (202505-05), 1 atom(s) (dev-lang/orc); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2024-40897
redhat medium https://access.redhat.com/security/cve/CVE-2024-40897
suse high CVE-2024-40897 severity important: SUSE including 42 source package names (0.3.2-1.2:liborc-0_4-0-0.4.28-150000.3.9.1, 0.3.32-3.4:liborc-0_4-0-0.4.28-150000.3.9.1, …), 167 product×package rows across 72 product lines (Container containers/lmcache-vllm-openai, Container containers/open-webui, … (72 product lines)): Fixed 166, Known Not Affected 1. https://www.suse.com/security/cve/CVE-2024-40897/
ubuntu medium CVE-2024-40897 medium priority: Ubuntu including 1 source packages (orc), 6 status rows across 6 suites (bionic, focal, jammy, noble, upstream, xenial): released 6. https://ubuntu.com/security/CVE-2024-40897

Affected software / configurations for CVE-2024-40897

Vendor Product Version Raw CPE
gstreamer orc < 0.4.39 cpe:2.3:a:gstreamer:orc:*:*:*:*:*:*:*:*

References for CVE-2024-40897

cvelogic Threat Intelligence