CVE-2024-37017
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 · uneditedasdcplib (aka AS-DCP Lib) 2.13.1 has a heap-based buffer over-read in ASDCP::TimedText::MXFReader::h__Reader::MD_to_TimedText_TDesc in AS_DCP_TimedText.cpp in libasdcp.so.
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 confidenceasdcplib 2.13.1 contains a heap-based buffer over-read vulnerability in the MD_to_TimedText_TDesc function when processing TimedText MXF files. The library reads beyond allocated heap memory boundaries, potentially causing denial of service or exposing sensitive memory contents.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify asdcplib installation and versionLocate the asdcplib library in your environment (common paths include /usr/lib/, /usr/local/lib/, or within application bundles). Check the library file name or version metadata (e.g., run 'file asdcplib.so' or inspect version info embedded in the binary).Affected if The installed version is 2.13.1 or an earlier version that contains the MD_to_TimedText_TDesc function in AS_DCP_TimedText.cpp
-
Confirm the vulnerable function existsInspect the asdcplib source or binary for the function named 'MD_to_TimedText_TDesc'. If you have access to source code, verify this function is present in AS_DCP_TimedText.cpp.Affected if The MD_to_TimedText_TDesc function is present in the asdcplib codebase being used
-
Determine if TimedText MXF processing is in useReview application logs, configuration, or code that uses asdcplib to determine if it processes TimedText MXF files (look for TimedText-related function calls or MXF file handling that involves timed text tracks).Affected if The application uses asdcplib to process TimedText MXF files, as the vulnerability triggers specifically when handling this file type
-
Check for heap boundary access patternsIf you have access to the source, review the MD_to_TimedText_TDesc function in AS_DCP_TimedText.cpp for buffer access operations that lack proper bounds checking before reading heap memory.Affected if The function contains buffer read operations without adequate boundary validation, which is the root cause of the over-read
A user is affected if they are running asdcplib version 2.13.1 (or earlier) and use it to process TimedText MXF files, enabling the vulnerable MD_to_TimedText_TDesc function to trigger the heap buffer over-read.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate asdcplib to a patched version that fixes the buffer boundary check in AS_DCP_TimedText.cpp. If a patched version is unavailable, implement bounds checking in the MD_to_TimedText_TDesc function before accessing heap buffers.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37017 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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