CVE-2012-3377
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 · uneditedHeap-based buffer overflow in the Ogg_DecodePacket function in the OGG demuxer (modules/demux/ogg.c) in VideoLAN VLC media player before 2.0.2 allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a crafted OGG 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 confidenceHeap-based buffer overflow in the Ogg_DecodePacket function in VLC's OGG demuxer (modules/demux/ogg.c) allows remote attackers to cause denial of service and potentially execute arbitrary code via a crafted OGG file. The vulnerability affects VLC media player versions prior to 2.0.2.
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<= 2.0.1= 0.1.99a= 0.1.99b= 0.1.99c= 0.1.99d= 0.1.99e= 0.1.99f= 0.1.99g= 0.1.99h= 0.1.99i= 0.2.0= 0.2.50CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/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.
-
Check if VLC is installedOn Windows: check Program Files\VideoLAN\VLC or run 'vlc --version' from command line. On Linux: run 'vlc --version' or check /usr/bin/vlc. On macOS: check /Applications/VLC.appAffected if VLC is installed and the version is 2.0.1 or earlier, or one of the specific versions listed (0.1.99a-0.2.50)
-
Determine the exact VLC versionRun 'vlc --version' from a terminal or command prompt. On Windows, you can also right-click the vlc.exe file, select Properties, and view the File Version under the Details tab.Affected if Version returned is 2.0.1 or lower, or matches 0.1.99a through 0.2.50 range
-
Verify OGG demuxer is presentCheck that the OGG demuxer module exists in the VLC installation. On Windows: look for modules\demux\ogg.dll in the VLC directory. On Linux: check for libogg_plugin.so in the plugins directory.Affected if The OGG demuxer module exists and the VLC version is in the affected range
You are affected if VLC media player version 2.0.1 or earlier (or specifically 0.1.99a through 0.2.50) is installed and the OGG demuxer module is present on the system.
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 2.0.2 or later. Avoid opening untrusted or unknown OGG files until the patch is applied.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2012-3377 — 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-2012-3377 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