Skip to content
Noroxi
NVD / CVE Program· CNA jpcert

CVE-2024-40897: Stack-based buffer overflow vulnerability exists in orcparse.c of ORC versions prior to 0.4.39.

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.37% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
  • Fixed version: azl3 orc 0.4.39-2 on Azure Linux 3.0 0.4.39-2.

Low priority for now. Upgrade to azl3 orc 0.4.39-2 on Azure Linux 3.0 0.4.39-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.7 · v3.1—No exploit Fix available
Published
Jul 26, 2024
Updated
Jun 17, 2026
EPSS
0.3% · 31th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-40897

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for gstreamer records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
gstreamerorc

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gstreamer orcbefore 0.4.39

Versions reported by the vendor

Affected version ranges reported by the assigning authority (jpcert). Independent of NVD's CPE analysis and usually ahead of it.

  • GStreamer ORC

    • prior to 0.4.39affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8orcbefore 0.4.28-4.el8_100.4.28-4.el8_10
AlmaLinux:8orc-compilerbefore 0.4.28-4.el8_100.4.28-4.el8_10
AlmaLinux:8orc-develbefore 0.4.28-4.el8_100.4.28-4.el8_10
AlmaLinux:9orcbefore 0.4.31-7.el9_40.4.31-7.el9_4
AlmaLinux:9orc-compilerbefore 0.4.31-7.el9_40.4.31-7.el9_4
AlmaLinux:9orc-develbefore 0.4.31-7.el9_40.4.31-7.el9_4
Alpine:v3.17orcbefore 0.4.39-r00.4.39-r0
Debian:12orcfrom 0—
Debian:13orcbefore 1:0.4.39-11:0.4.39-1
openSUSE:Leap 15.6orcbefore 0.4.28-150000.3.9.10.4.28-150000.3.9.1
openSUSE:Leap Micro 5.5orcbefore 0.4.28-150000.3.6.10.4.28-150000.3.6.1
openSUSE:Tumbleweedorcbefore 0.4.39-1.10.4.39-1.1
Red Hat:enterprise_linux:8::appstreamorcbefore 0:0.4.28-4.el8_100:0.4.28-4.el8_10
Red Hat:enterprise_linux:8::appstreamorc-compilerbefore 0:0.4.28-4.el8_100:0.4.28-4.el8_10
Red Hat:enterprise_linux:8::appstreamorc-compiler-debuginfobefore 0:0.4.28-4.el8_100:0.4.28-4.el8_10
Red Hat:enterprise_linux:8::appstreamorc-debuginfobefore 0:0.4.28-4.el8_100:0.4.28-4.el8_10
Red Hat:enterprise_linux:8::appstreamorc-debugsourcebefore 0:0.4.28-4.el8_100:0.4.28-4.el8_10
Red Hat:enterprise_linux:8::appstreamorc-develbefore 0:0.4.28-4.el8_100:0.4.28-4.el8_10
Red Hat:enterprise_linux:9::appstreamorcbefore 0:0.4.31-7.el9_40:0.4.31-7.el9_4
Red Hat:enterprise_linux:9::appstreamorc-compilerbefore 0:0.4.31-7.el9_40:0.4.31-7.el9_4
Red Hat:enterprise_linux:9::appstreamorc-compiler-debuginfobefore 0:0.4.31-7.el9_40:0.4.31-7.el9_4
Red Hat:enterprise_linux:9::appstreamorc-debuginfobefore 0:0.4.31-7.el9_40:0.4.31-7.el9_4
Red Hat:enterprise_linux:9::appstreamorc-debugsourcebefore 0:0.4.31-7.el9_40:0.4.31-7.el9_4
Red Hat:enterprise_linux:9::appstreamorc-develbefore 0:0.4.31-7.el9_40:0.4.31-7.el9_4

+32

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 orc 0.4.39-2 on Azure Linux 3.00.4.39-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:orc0.4.28-4.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:orc-compiler0.4.28-4.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:orc-devel0.4.28-4.el8_10 · AlmaLinux:8Package registry (OSV)
alpine:orc0.4.39-r0 · Alpine:v3.17Package registry (OSV)
debian:orc1:0.4.39-1 · Debian:13Package registry (OSV)
opensuse:orc0.4.28-150000.3.6.1 · openSUSE:Leap Micro 5.5Package registry (OSV)
red hat:orc0:0.4.28-4.el8_10 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:orc-compiler0:0.4.28-4.el8_10 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:orc-compiler-debuginfo0:0.4.28-4.el8_10 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:orc-debuginfo0:0.4.28-4.el8_10 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:orc-debugsource0:0.4.28-4.el8_10 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
red hat:orc-devel0:0.4.28-4.el8_10 · Red Hat:enterprise_linux:8::appstreamPackage registry (OSV)
rocky linux:orc0:0.4.28-4.el8_10 · Rocky Linux:8Package registry (OSV)
suse:orc0.4.21-3.3.1 · SUSE:Linux Enterprise Software Development Kit 12 SP5Package registry (OSV)
suse:orc0.4.28-150000.3.6.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records