dbcve.org
Libde265Application · Struktur

CVE-2024-38949

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Heap Buffer Overflow vulnerability in Libde265 v1.0.15 allows attackers to crash the application via crafted payload to display444as420 function at sdl.cc

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 · moderate confidence

Heap buffer overflow vulnerability in Libde265 v1.0.15 in the display444as420 function in sdl.cc allows attackers to corrupt heap memory via specially crafted HEIC/H.265 files, potentially causing application crash or arbitrary code execution.

MitigationUpgrade to patched version of Libde265 if available; implement proper bounds checking in display444as420 function; validate input file dimensions and format specifications before processing.

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
Libde265Application
Affected:= 1.0.15

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 Libde265 is installed
    Run 'pkg-config --modversion libde265' or check for libde265.so/.a files in common library directories (e.g., /usr/lib/, /usr/local/lib/)
    Affected if Libde265 version equals 1.0.15 exactly
  2. Verify the installed Libde265 version
    Check the version string returned by pkg-config, or run 'ldd your_application | grep de265' to find linked library version, or inspect the shared object file with 'readelf -d libde265.so | grep VERSION'
    Affected if Version reported is 1.0.15
  3. Determine if SDL display functionality is in use
    Check if the application links against both libde265 and libsdl2 (ldd your_app | grep -E 'de265|sdl2'), or inspect binary for references to 'display444as420' symbol
    Affected if SDL2 is linked and the display444as420 function from sdl.cc would be invoked
  4. Identify if HEIC or H.265 file processing occurs
    Review application logs, configuration, or source code for HEIC/H.265 file opening/processing (look for .heic, .h265 extensions or CODEC_ID_HEVC in media applications)
    Affected if The application processes HEIC or H.265 media files using the vulnerable Libde265 library

You are affected if Libde265 version 1.0.15 is installed AND your application uses SDL display functionality to render HEIC/H.265 files, enabling the vulnerable display444as420 code path in sdl.cc.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to patched version of Libde265 if available; implement proper bounds checking in display444as420 function; validate input file dimensions and format specifications before processing.

Recommended fix Moderate confidence

Libde265 1.0.16 or latest stable release

  1. 1. Identify all applications or services that link to or use Libde265 version 1.0.15
  2. 2. Check the application's dependency manifests (e.g., package.json, Cargo.toml, CMakeLists.txt, package manager lock files) for the Libde265 dependency
  3. 3. Update the dependency specification to request Libde265 version 1.0.16 or later
  4. 4. Run dependency update commands appropriate to your package manager (e.g., npm update, cargo update, pip install -U)
  5. 5. Rebuild and recompile the application to link against the updated library
  6. 6. Test the rebuilt application to ensure functionality remains intact
  7. 7. Deploy the updated application to production environments
Caveat Verify compatibility with any application features that directly interface with libde265 APIs; minor version upgrades typically have backward compatibility but test thoroughly

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

Fix this in Libde265 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38949 — 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-38949 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