CVE-2010-2937
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 · uneditedThe ReadMetaFromId3v2 function in taglib.cpp in the TagLib plugin in VideoLAN VLC media player 0.9.0 through 1.1.2 does not properly process ID3v2 tags, which allows remote attackers to cause a denial of service (application crash) via a crafted media file.
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 confidenceThe TagLib plugin in VLC media player versions 0.9.0-1.1.2 contains a vulnerability in the ReadMetaFromId3v2 function in taglib.cpp. The function fails to properly validate or bounds-check data when processing ID3v2 metadata tags, allowing a specially crafted media file to trigger a denial of service via application crash.
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= 0.9.0= 0.9.1= 0.9.2= 0.9.3= 0.9.4= 0.9.5= 0.9.6= 0.9.7= 0.9.8a= 0.9.9= 0.9.9a= 0.9.10CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 installed VLC versionRun 'vlc --version' from command line, or open VLC and navigate to Help > About to view the version numberAffected if Version is between 0.9.0 and 0.9.10 inclusive (or any version 1.1.2 or earlier that includes the vulnerable TagLib library)
-
Locate TagLib pluginFind the TagLib plugin file in the VLC plugins directory (typically /usr/lib/vlc/plugins or C:\Program Files\VideoLAN\VLC\plugins on Windows)Affected if The libtaglib_plugin file exists in the VLC plugins folder
-
Verify ID3v2 tag processing capabilityThe vulnerability exists in the ReadMetaFromId3v2 function. Check if the TagLib plugin handles ID3v2 metadata by opening a media file and inspecting metadata via Tools > Media InformationAffected if ID3v2 metadata tags can be read by VLC using the TagLib plugin
You are affected if VLC version is 0.9.0 through 0.9.10 (or the vulnerable TagLib-enabled version) and you open media files containing ID3v2 metadata tags.
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 dataUpgrade VLC media player to version 1.1.3 or later, which contains the patched TagLib library. Alternatively, avoid opening untrusted media files from unknown or untrusted sources.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2937 — 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-2010-2937 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