ChromeWeb browser · Google
CVE-2013-0899
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 padding implementation in the opus_packet_parse_impl function in src/opus_decoder.c in Opus before 1.0.2, as used in Google Chrome before 25.0.1364.97 on Windows and Linux and before 25.0.1364.99 on Mac OS X and other products, allows remote attackers to cause a denial of service (out-of-bounds read) via a long packet.
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 confidenceInteger overflow in the padding implementation of opus_packet_parse_impl in src/opus_decoder.c allows remote attackers to trigger an out-of-bounds read via a crafted long Opus packet, causing denial of service. The vulnerability exists in Opus before version 1.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
ChromeWeb browser
< 25.0.1364.97< 25.0.1364.99< 1.0.2= 12.1= 12.2CVSS 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 Opus library versionRun 'opusinfo' or check libopus package version (dpkg -l libopus0, rpm -q libopus, or similar package manager command)Affected if Version is lower than 1.0.2
-
Identify Google Chrome versionOpen Chrome, go to Settings > About Chrome, or run 'google-chrome --version' or 'chrome --version' in terminalAffected if Version is lower than 25.0.1364.97 (Windows/Linux) or lower than 25.0.1364.99 (Mac OS X)
-
Check for presence of vulnerable Opus decoderLocate libopus decoder binary or library file (libopus.so, libopus.dylib, or opus_decoder binary) and verify build date or version metadataAffected if The library binary predates the 1.0.2 release (approximately February 2013) or version cannot be determined to be 1.0.2 or later
-
Determine if application processes Opus audio dataInspect running processes or application logs for Opus decoding activity (look for 'opus' in process list, audio codec usage logs, or network traffic analysis for Opus RTP packets)Affected if Any application or service processes untrusted Opus packets without validation and uses a library version < 1.0.2
Your environment is affected if you use any version of Opus library before 1.0.2, or Google Chrome before 25.0.1364.97/25.0.1364.99, and that software processes Opus audio data.
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 data1.0.225.0.1364.9725.0.1364.99
Update Opus library to version 1.0.2 or later, or update Google Chrome to version 25.0.1364.97+ (Windows/Linux) or 25.0.1364.99+ (Mac OS X) to receive the patched library.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0899 — 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-2013-0899 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