Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-14632

libvorbis: Invalid freeing of uninitialized memory in the function vorbis_analysis_headerout()

Overview

Published
21 Sep 2017
Modified
17 Jun 2026
Critical CVE
0 Registry packages
9 OS packages
4 Linux distributions
Yes Fix available

Description

Xiph.Org libvorbis 1.3.5 allows Remote Code Execution upon freeing uninitialized memory in the function vorbis_analysis_headerout() in info.c when vi->channels<=0, a similar issue to Mozilla bug 550184.

Source: OX vulnerability database

Severity

9.8 · CRITICAL

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-119

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 11 fixes

alpine 4 releases · 1 package

fixed 4
libvorbis
alpine fixes for CVE-2017-14632
ReleasePackageFixed in
3.22 libvorbis 1.3.5-r4
3.23 libvorbis 1.3.5-r4
3.24 libvorbis 1.3.5-r4
edge libvorbis 1.3.5-r4

debian 5 releases · 1 package

fixed 5
libvorbis
debian fixes for CVE-2017-14632
ReleasePackageFixed in
11 libvorbis 1.3.5-4.1
12 libvorbis 1.3.5-4.1
13 libvorbis 1.3.5-4.1
14 libvorbis 1.3.5-4.1
9 libvorbis 1.3.5-4+deb9u1

echo 1 release · 1 package

fixed 1
libvorbis
echo fixes for CVE-2017-14632
ReleasePackageFixed in
libvorbis 1.3.5-4.1

openSUSE 1 release · 1 package

fixed 1
libvorbis-devel
openSUSE fixes for CVE-2017-14632
ReleasePackageFixed inAdvisory
Tumbleweed libvorbis-devel +7 1.3.7-1.6 openSUSE-SU-2024:11009-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.