CVE-2010-4705
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 · uneditedInteger overflow in the vorbis_residue_decode_internal function in libavcodec/vorbis_dec.c in the Vorbis decoder in FFmpeg, possibly 0.6, has unspecified impact and remote attack vectors, related to the sizes of certain integer data types. NOTE: this might overlap CVE-2011-0480.
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 confidenceInteger overflow vulnerability in the vorbis_residue_decode_internal function within FFmpeg's Vorbis audio decoder (libavcodec/vorbis_dec.c). The overflow occurs when processing Vorbis audio files due to improper handling of integer data type sizes during residue decoding, potentially allowing remote code execution or denial of service when processing maliciously crafted audio files.
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.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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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.
-
Check installed FFmpeg versionRun 'ffmpeg -version' or 'ffmpeg -version 2>&1' to display the version informationAffected if The displayed version is exactly 0.6 (or falls within 0.6.x if other 0.6 variants exist in the affected range)
-
Verify FFmpeg build includes Vorbis supportRun 'ffmpeg -codecs 2>&1 | grep -i vorbis' or 'ffmpeg -decoders 2>&1 | grep -i vorbis' to list Vorbis decodersAffected if Vorbis audio decoders (such as vorbis) appear in the available codecs list, indicating the vulnerable decoder is present in the build
-
Confirm libavcodec version if using librariesIf linking against libavcodec directly, check the library file version via 'pkg-config --modversion libavcodec' or inspect the shared object (for example: 'ls -la /usr/lib/libavcodec.so*')Affected if The library version resolves to 0.6, confirming the vulnerable library is in use
-
Identify active FFmpeg binaries using VorbisRun 'which ffmpeg' to locate the binary, then examine any running processes via 'ps aux | grep ffmpeg' or review application logs that process audio filesAffected if FFmpeg is actively being used or scheduled to process audio files, particularly those with .ogg or other Vorbis-encoded extensions
You are affected if FFmpeg version 0.6 is installed and your environment processes or is capable of processing Vorbis audio files using the vulnerable vorbis_dec.c decoder component.
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 FFmpeg to a patched version that addresses the integer overflow in the Vorbis decoder. If updates are not possible, disable or restrict processing of untrusted Vorbis audio files.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-4705 — 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-4705 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