dbcve.org
LibvorbisApplication · Xiph.org

CVE-2008-1423

HIGH · 9.3 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 →
100/100
Remediation priority · Urgent
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 a certain quantvals and quantlist calculation in Xiph.org libvorbis 1.2.0 and earlier allows remote attackers to cause a denial of service (crash) or execute arbitrary code via a crafted OGG file with a large virtual space for its codebook, 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 quantvals and quantlist calculation in Xiph.org libvorbis 1.2.0 and earlier allows remote attackers to cause a denial of service or execute arbitrary code via a crafted OGG file with a large virtual space for its codebook, triggering a heap overflow.

MitigationUpgrade to a patched version of libvorbis (post-1.2.0) and/or ensure OGG files from untrusted sources are not processed without validation.

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.1.2= 1.2.0

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

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

  1. Identify installed libvorbis version
    Run 'pkg-config --modversion vorbis' or check the library file with 'ldd' against your application, or examine the package manager output (dpkg -l libvorbis0, rpm -q libvorbis, etc.)
    Affected if The version is 1.0.0, 1.0.1, 1.1.0, 1.1.1, 1.1.2, or 1.2.0
  2. Locate libvorbis library files
    Find libvorbis files with 'find /usr -name "*vorbis*" -type f' and check soname with 'objdump -p /path/to/libvorbis.so | grep SONAME'
    Affected if The library file is present and version matches affected versions from step 1
  3. Determine if applications process OGG media files
    Audit running processes or scheduled tasks that decode OGG files, or inspect configuration files for media processing software (players, transcoders, etc.)
    Affected if Any application uses libvorbis to decode OGG files, especially from untrusted or network sources
  4. Check for vulnerable code presence
    If you have access to the libvorbis source or binary, search for the quantvals/quantlist calculation functions in the codebook.c or related files and verify the lack of integer overflow checks
    Affected if The code lacks proper bounds checking on codebook dimension calculations before memory allocation
  5. Review OGG file processing behavior
    Monitor or audit systems that accept OGG file uploads, ingest OGG streams from network sources, or process OGG files in containerized workloads
    Affected if Untrusted OGG files are processed without prior validation or sanitization
  6. Identify linked applications
    Use 'ldd /path/to/binary' on media players, transcoders, or any vorbis-enabled applications to confirm libvorbis linkage, then check application versions for standalone patches
    Affected if Applications link against the affected libvorbis versions and handle OGG input

You are affected if libvorbis version 1.0.0 through 1.2.0 is installed and any application uses it to process OGG files, particularly 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of libvorbis (post-1.2.0) and/or ensure OGG files from untrusted sources are not processed without validation.

Recommended fix Moderate confidence

libvorbis 1.2.1 or later (latest stable release)

  1. 1. Identify all systems and applications using the affected libvorbis versions (1.0.0, 1.0.1, 1.1.0, 1.1.1, or 1.2.0 and earlier).
  2. 2. Locate the libvorbis library package in your system (commonly found in /usr/lib/, /usr/local/lib/, or bundled within applications).
  3. 3. Download the latest stable libvorbis release from the official Xiph.org repository (https://xiph.org/vorbis/) or your distribution's package manager.
  4. 4. Compile and install the new version, ensuring to update any applications that link against libvorbis.
  5. 5. Restart any services or applications that use libvorbis to load the updated library.
  6. 6. Verify the installed version matches a release later than 1.2.0 (such as 1.2.1 or latest stable).
Caveat Minor: Applications statically linked with vulnerable libvorbis versions will need recompilation; ensure API/ABI compatibility if using custom integrations.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Libvorbis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Check whether your project pulls in CVE-2008-1423 — 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-1423 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