Skip to content
Noroxi
CVE-2007-4066· NVD / CVE Program· CNA redhat

Multiple buffer overflows in Xiph.Org libvorbis before 1.2.0 allow context-dependent attackers to cause a denial of service or have other un

Multiple buffer overflows in Xiph.Org libvorbis before 1.2.0 allow context-dependent attackers to cause a denial of service or have other unspecified impact via a crafted OGG file, aka trac Changesets 13162, 13168, 13169, 13170, 13172, 13211, and 13215, as demonstrated by an overflow in oggenc.exe related to the _psy_noiseguards_8 array.

MediumCVSS 4.3 · v2.0—No exploit Fix available
Published
Sep 21, 2007
Updated
Jun 16, 2026
EPSS
1.8% · 78th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.8%

Affected systems

VendorProduct
xiph.orglibvorbis

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • xiph.org libvorbisup to 1.2.0 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12libvorbisbefore 1.2.0.dfsg-11.2.0.dfsg-1
Debian:12libvorbisidecbefore 1.0.2+svn16259-21.0.2+svn16259-2
Debian:3.1libvorbisbefore 1.1.0-21.1.0-2
Debian:4.0libvorbisbefore 1.1.2.dfsg-1.31.1.2.dfsg-1.3
Red Hat:enterprise_linux:2.1::aslibvorbisbefore 0:1.0rc2-7.el20:1.0rc2-7.el2
Red Hat:enterprise_linux:2.1::aslibvorbis-develbefore 0:1.0rc2-7.el20:1.0rc2-7.el2
Red Hat:enterprise_linux:3::aslibvorbisbefore 1:1.0-8.el31:1.0-8.el3
Red Hat:enterprise_linux:3::aslibvorbis-debuginfobefore 1:1.0-8.el31:1.0-8.el3
Red Hat:enterprise_linux:3::aslibvorbis-develbefore 1:1.0-8.el31:1.0-8.el3
Red Hat:enterprise_linux:4::aslibvorbisbefore 1:1.1.0-2.el4.51:1.1.0-2.el4.5
Red Hat:enterprise_linux:4::aslibvorbis-debuginfobefore 1:1.1.0-2.el4.51:1.1.0-2.el4.5
Red Hat:enterprise_linux:4::aslibvorbis-develbefore 1:1.1.0-2.el4.51:1.1.0-2.el4.5
Red Hat:enterprise_linux:5::client_workstationlibvorbisbefore 1:1.1.2-3.el5.01:1.1.2-3.el5.0
Red Hat:enterprise_linux:5::client_workstationlibvorbis-debuginfobefore 1:1.1.2-3.el5.01:1.1.2-3.el5.0
Red Hat:enterprise_linux:5::client_workstationlibvorbis-develbefore 1:1.1.2-3.el5.01:1.1.2-3.el5.0

Other highest-scoring records for the same primary product.

  • CVE-2017-14632Xiph.Org libvorbis 1.3.5 allows Remote Code Execution upon freeing uninitialized memory in the function vorbis_analysis_headerout() in info.
    41Plan
  • CVE-2008-1423Integer overflow in a certain quantvals and quantlist calculation in Xiph.org libvorbis 1.2.0 and earlier allows remote attackers to cause a
    39Monitor
  • CVE-2018-10392mapping0_forward in mapping0.c in Xiph.Org libvorbis 1.3.6 does not validate the number of channels, which allows remote attackers to cause
    36Monitor
  • CVE-2017-14160The bark_noise_hybridmp function in psy.c in Xiph.Org libvorbis 1.3.5 allows remote attackers to cause a denial of service (out-of-bounds ac
    36Monitor
  • CVE-2018-10393bark_noise_hybridmp in psy.c in Xiph.Org libvorbis 1.3.6 has a stack-based buffer over-read.
    31Monitor
  • CVE-2008-1420Integer overflow in residue partition value (aka partvals) evaluation in Xiph.org libvorbis 1.2.0 and earlier allows remote attackers to exe
    29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:libvorbis1.2.0.dfsg-1 · Debian:12Package registry (OSV)
debian:libvorbisidec1.0.2+svn16259-2 · Debian:12Package registry (OSV)
red hat:libvorbis1:1.0-8.el3 · Red Hat:enterprise_linux:3::asPackage registry (OSV)
red hat:libvorbis-debuginfo1:1.0-8.el3 · Red Hat:enterprise_linux:3::asPackage registry (OSV)
red hat:libvorbis-devel1:1.0-8.el3 · Red Hat:enterprise_linux:3::asPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    none
    Integrity
    none
    Availability
    P · the service can be disrupted
    Attack complexity
    M
    Confidentiality impact
    None
    Integrity impact
    None
    Availability impact
    P

    CVSS vector

    AV:N/AC:M/Au:N/C:N/I:N/A:P

    nvd-primary

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    All records