CVE-2012-2792
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 · uneditedUnspecified vulnerability in the decode_init function in libavcodec/wmalosslessdec.c in FFmpeg before 0.11 has unknown impact and attack vectors, related to the samples per frame.
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 confidenceA vulnerability in the decode_init function of the WMA Lossless decoder (libavcodec/wmalosslessdec.c) in FFmpeg versions prior to 0.11 allows unspecified impact via manipulation of the samples per frame parameter during decoder initialization, likely enabling memory corruption or out-of-bounds access.
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.10.4= 0.3= 0.3.1= 0.3.2= 0.3.3= 0.3.4= 0.4.0= 0.4.2= 0.4.3= 0.4.4= 0.4.5= 0.4.6CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 FFmpeg versionRun 'ffmpeg -version' or 'avconv -version' to display version information. Look for the version number in the output (e.g., 'ffmpeg version 0.10.4').Affected if The version is 0.10.4 or lower, or matches any of these: 0.3, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.4.0, 0.4.2, 0.4.3, 0.4.4, 0.4.5, or 0.4.6.
-
Check if WMA Lossless decoder is availableRun 'ffmpeg -decoders' or 'avconv -decoders' and search for 'wmalossless' in the output list of available audio decoders.Affected if The wmalossless decoder is listed as available and the FFmpeg version falls within the affected range.
-
Verify WMA Lossless support was compiled inRun 'ffmpeg -formats' or check the libavcodec/wmalosslessdec.c file presence in the installation directory. Alternatively, use 'ffmpeg -h decoder=wmalossless' to query decoder help.Affected if WMA Lossless decoding support is compiled into the FFmpeg build and the version is affected.
-
Inspect running processes using FFmpeg for WMA handlingReview any application logs, transcoding jobs, or media processing scripts that handle .wmal, .wmals, or WMA Lossless files. Use 'ps aux | grep ffmpeg' to find running FFmpeg processes and examine their command arguments for WMA file inputs.Affected if FFmpeg is actively processing WMA Lossless audio files and the version is within the affected range.
You are affected if FFmpeg version 0.10.4 or lower, or any version from 0.3 through 0.4.6, is installed AND the WMA Lossless decoder is available or being used to process WMA Lossless audio files.
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.
dbcve · scopedUpgrade to FFmpeg 0.11 or later to obtain the patched version of the WMA Lossless decoder. Audit any applications or services that process WMA Lossless audio files using the affected FFmpeg version.
FFmpeg 0.11 or later
- Upgrade FFmpeg to version 0.11 or later to resolve the vulnerability in the decode_init function in libavcodec/wmalosslessdec.c
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2792 — 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-2792 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