ChromeWeb browser · Google
CVE-2014-7937
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 · uneditedMultiple off-by-one errors in libavcodec/vorbisdec.c in FFmpeg before 2.4.2, as used in Google Chrome before 40.0.2214.91, allow remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via crafted Vorbis I data.
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 confidenceOff-by-one errors in libavcodec/vorbisdec.c in FFmpeg allow memory corruption during Vorbis I audio decoding, leading to use-after-free conditions that can be exploited remotely via crafted audio files to cause denial of service or potentially execute arbitrary code.
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
ChromeWeb browser
<= 40.0.2214.85<= 2.4.1CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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 installed FFmpeg versionRun `ffmpeg -version` in a terminal and locate the version string in the output (typically in the format 'ffmpeg version X.X.X')Affected if The reported version is 2.4.1 or earlier
-
Check installed Google Chrome versionOpen Chrome and navigate to chrome://version, or run `google-chrome --version` on Linux / `Chrome --version` on Windows in a command promptAffected if The reported version is 40.0.2214.85 or earlier
-
Verify if Vorbis audio decoding is in useInspect your media processing pipeline or logs to determine if the system decodes Vorbis I audio files (.ogg extension). Check for applications that process audio files using FFmpeg's libavcodec libraryAffected if Vorbis I audio decoding is performed using an affected FFmpeg library version
-
Identify libavcodec version in useIf FFmpeg is used as a library by another application, check the application's dependency on libavcodec by running `ldd <application_binary> | grep avcodec` on Linux, or examine the linked libavcodec DLL version on WindowsAffected if The linked libavcodec version corresponds to FFmpeg 2.4.1 or earlier
You are affected if you are running FFmpeg 2.4.1 or earlier, or Google Chrome 40.0.2214.85 or earlier, and your environment processes Vorbis I audio files using the vulnerable libavcodec library.
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 version 2.4.2 or later, or update Google Chrome to version 40.0.2214.91 or later to incorporate the patched libavcodec library.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7937 — 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-2014-7937 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