dbcve.org
LibvorbisApplication

CVE-2007-4029

MEDIUM · 6.8 CVSS v2.0 Published 2007-07-26
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
libvorbis 1.1.2, and possibly other versions before 1.2.0, allows context-dependent attackers to cause a denial of service via (1) an invalid mapping type, which triggers an out-of-bounds read in the vorbis_info_clear function in info.c, and (2) invalid blocksize values that trigger a segmentation fault in the read function in block.c.

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

libvorbis 1.1.2 and earlier versions contain two denial-of-service vulnerabilities: an invalid mapping type triggers an out-of-bounds read in vorbis_info_clear() in info.c, and invalid blocksize values cause a segmentation fault in the read function in block.c. Both are triggered by malformed Vorbis audio files.

MitigationUpgrade libvorbis to version 1.2.0 or later to patch both vulnerabilities. Ensure any software bundling or linking against libvorbis is also updated.

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

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 version
    Run 'dpkg -l libvorbis0' on Debian/Ubuntu, 'rpm -q libvorbis' on RHEL/CentOS, or 'pkg_info -L libvorbis' on FreeBSD. If no package manager access, examine the shared library: 'ls -la /usr/lib/libvorbis*' and check the symlink target for version numbers.
    Affected if The installed version is 1.1.2 or any version earlier than 1.1.2 (such as 1.1.1, 1.1.0, or 1.0.x series).
  2. Confirm libvorbis is linked to running applications
    Run 'ldd /path/to/application | grep vorbis' on any audio player, media converter, or streaming software on the system. Common applications that link libvorbis include FFmpeg, VLC, Audacity, MPlayer, and Firefox.
    Affected if Any application that processes Vorbis audio files is linked against the vulnerable libvorbis version found in step 1.
  3. Verify the application processes Vorbis audio files
    Check if the linked application accepts .ogg, .oga, or Vorbis-encoded audio input. Test with a sample Vorbis file or review the application's supported formats documentation.
    Affected if The application processes untrusted or user-supplied Vorbis audio files, allowing malformed files to reach the libvorbis decoder.

Your environment is affected if libvorbis version 1.1.2 or earlier is installed AND any application on the system links to it to process Vorbis audio files.

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

Upgrade libvorbis to version 1.2.0 or later to patch both vulnerabilities. Ensure any software bundling or linking against libvorbis is also updated.

Fix this in Libvorbis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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