Skip to content
Fencer Intel
low 2.1

CVE-2014-9496 json

The sd2_parse_rsrc_fork function in sd2.c in libsndfile allows attackers to have unspecified impact via vectors related to a (1) map offset…

published 2015-01-16 11 y ago modified 2026-06-17 4 mo ago also EUVD-2014-9313

cvss
2.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

The sd2_parse_rsrc_fork function in sd2.c in libsndfile allows attackers to have unspecified impact via vectors related to a (1) map offset or (2) rsrc marker, which triggers an out-of-bounds read.

Patch / fix

  • libsndfile_project libsndfile 1.0.26
  • libsndfile Debian 14, Debian 13, Debian 12 1.0.25-9.1

debian advisories DEBIAN-CVE-2014-9496

  • libsndfile Ubuntu 14.04 LTS 1.0.25-7ubuntu2.1

ubuntu advisories UBUNTU-CVE-2014-9496

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libsndfile openSUSE Tumbleweed 1.0.26-2.4
  • libsndfile-progs openSUSE Tumbleweed 1.0.26-2.4

opensuse advisories openSUSE-SU-2024:10148-1openSUSE-SU-2024:10470-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-9496 updated cvss 1.2

libsndfile: 2 buffer overruns in sd2_parse_rsrc_fork()

  • Red Hat Enterprise Linux 6 libsndfile Red Hat Enterprise Linux 7 libsndfile, libsndfile-utils
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.58% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/erikd/libsndfile/issues/93 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:N/A:P

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.