dbcve.org
LibvorbisApplication · Xiph.org

CVE-2008-1420

MEDIUM · 6.8 CVSS v2.0 Published 2008-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Integer overflow in residue partition value (aka partvals) evaluation in Xiph.org libvorbis 1.2.0 and earlier allows remote attackers to execute arbitrary code via a crafted OGG file, which triggers a heap overflow.

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 confidence

Integer overflow in the residue partition value (partvals) evaluation in Xiph.org libvorbis 1.2.0 and earlier allows remote attackers to execute arbitrary code via a crafted OGG file, triggering a heap overflow.

MitigationUpdate libvorbis to a version newer than 1.2.0 that contains the patched integer overflow fix. Applications bundling or linking against libvorbis should rebuild against the updated library.

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
LibvorbisApplication
Affected:= 1.0.0= 1.0.1= 1.1.0= 1.1.1= 1.2.0= 1.12

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed libvorbis library version
    On Linux: run `pkg-config --modversion vorbis` or check with `ldd --version` or `dpkg -l | grep libvorbis`. On Windows: right-click vorbis.dll or libvorbis.dll and select Properties > Details to view File Version.
    Affected if The version matches 1.0.0, 1.0.1, 1.1.0, 1.1.1, 1.2.0, or 1.12 (if applicable) - all are within the vulnerable range.
  2. Check if libvorbis is used to process OGG files
    Identify applications on the system that link against libvorbis and process OGG media files. Use `ldd <application>` on Linux or examine dependencies on Windows with tools like Dependency Walker.
    Affected if Any application uses libvorbis to decode OGG files and processes files from untrusted sources.
  3. Determine if OGG files from untrusted sources can be processed
    Review application configurations and user workflows to identify whether OGG files from email attachments, downloads, network streams, or user-uploaded content are processed.
    Affected if The system or any application using libvorbis can be triggered to parse a maliciously crafted OGG file.

You are affected if your installed libvorbis version is 1.2.0 or earlier AND an application uses it to process OGG files, especially from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update libvorbis to a version newer than 1.2.0 that contains the patched integer overflow fix. Applications bundling or linking against libvorbis should rebuild against the updated library.

Fix this in Libvorbis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-1420 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-1420 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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