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

libsndfile: Information disclosure via aiff_read_chanmap() function

Overview

Published
12 Jun 2017
Modified
17 Jun 2026
High CVE
0 Registry packages
6 OS packages
5 Linux distributions
Yes Fix available

Description

In libsndfile version 1.0.28, an error in the "aiff_read_chanmap()" function (aiff.c) can be exploited to cause an out-of-bounds read memory access via a specially crafted AIFF file.

Source: OX vulnerability database

Severity

8.8 · HIGH

CVSS 3.0 base score, scored by NVD.

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 · 9 fixes

Red Hat 1 release · 1 package

wont fix 1
libsndfile
Red Hat fixes for CVE-2017-6892
ReleasePackageFixed in
7 libsndfile +2 wont fix

debian 5 releases · 1 package

fixed 5
libsndfile
debian fixes for CVE-2017-6892
ReleasePackageFixed in
11 libsndfile 1.0.28-1
12 libsndfile 1.0.28-1
13 libsndfile 1.0.28-1
14 libsndfile 1.0.28-1
9 libsndfile 1.0.27-3+deb9u1

echo 1 release · 1 package

fixed 1
libsndfile
echo fixes for CVE-2017-6892
ReleasePackageFixed in
libsndfile 1.0.28-1

openSUSE 1 release · 1 package

fixed 1
libsndfile-devel
openSUSE fixes for CVE-2017-6892
ReleasePackageFixed inAdvisory
Tumbleweed libsndfile-devel +2 1.0.31-2.2 openSUSE-SU-2024:10992-1

root.io debian 1 release · 1 package

fixed 1
rootio-libsndfile
root.io debian fixes for CVE-2017-6892
ReleasePackageFixed in
12 rootio-libsndfile 1.0.28-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.