dbcve.org
OrcApplication · Gstreamer

CVE-2024-40897

MEDIUM · 6.7 CVSS v3.1 Published 2024-07-26
Fix available
A fix is available. Upgrade to 0.4.39 or later.
See remediation →
67/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stack-based buffer overflow vulnerability exists in orcparse.c in ORC (Open Computation Reader) library versions prior to 0.4.39. When a developer processes a specially crafted malicious ORC file, the overflow allows arbitrary code execution in the context of the developer's build environment.

MitigationUpgrade ORC library to version 0.4.39 or later. Until then, avoid processing untrusted ORC files in developer machines and CI build environments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OrcApplication
Affected:< 0.4.39

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if ORC library is installed
    Run 'pkg-config --modversion orc-0.4' on Linux, check /usr/lib/liborc* for the library file, or query your system's package manager (dpkg -l | grep orc, rpm -qa | grep orc, brew list orc)
    Affected if ORC library version is found and is less than 0.4.39
  2. Check ORC library version number
    Execute 'pkg-config --modversion orc-0.4' or 'ldd --version' does not show ORC; instead check the library file directly: 'ls -la /usr/lib/x86_64-linux-gnu/liborc*' and compare the version in the filename, or run 'orc-version' if available
    Affected if The installed ORC library version is below 0.4.39
  3. Detect ORC usage in build environment
    Search your project for ORC references: 'grep -r "orc" --include="*.c" --include="*.h" .' and check build logs for '-lorc' linker flags or #include <orc/orc.h> statements
    Affected if Build scripts, source code, or dependencies reference the ORC library
  4. Check for ORC file processing
    Review your application logs, build outputs, or CI pipeline scripts for calls to functions that parse .orc files, or grep for orcParse, orc_compile, or similar ORC API functions in your codebase
    Affected if The application processes ORC files from any source, especially untrusted input
  5. Inspect ORC development headers
    Look for orc.h header file location: 'find /usr -name "orc.h" 2>/dev/null' and check the header version comment inside or examine the accompanying orc-version.h if present
    Affected if ORC headers exist and their version is not 0.4.39 or later

You are affected if the ORC library version installed in your build environment is lower than 0.4.39 and your code or CI pipeline processes ORC files, particularly from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.4.39 or later
Fixed in 0.4.39
Interim mitigation

Upgrade ORC library to version 0.4.39 or later. Until then, avoid processing untrusted ORC files in developer machines and CI build environments.

Recommended fix High confidence

ORC 0.4.39

  1. Check the currently installed ORC version using 'orc-config --version' or your system's package manager
  2. Upgrade ORC to version 0.4.39 or later. For systems using apt: 'sudo apt update && sudo apt install liborc-0.4-dev' (or the equivalent package for your distribution)
  3. For systems using other package managers, use: yum/dnf: 'sudo yum/dnf update orc' or brew: 'brew upgrade orc'
  4. For building from source, download ORC 0.4.39 or later from the official GStreamer source (gstreamer.freedesktop.org/src/orc/) and rebuild
  5. Verify the installed version matches or exceeds 0.4.39 using 'orc-config --version'

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Orc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-40897 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-40897 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data