Skip to content
Fencer Intel
medium 6.8

CVE-2011-2696 json

Integer overflow in libsndfile before 1.0.25 allows remote attackers to cause a denial of service (application crash) or possibly execute a…

published 2011-07-27 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2677

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

Summary

Integer overflow in libsndfile before 1.0.25 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted PARIS Audio Format (PAF) file that triggers a heap-based buffer overflow.

Patch / fix

  • libsndfile Debian 14, Debian 13, Debian 12 1.0.25-1

debian advisories DEBIAN-CVE-2011-2696

  • libsndfile RHEL 6 1.0.20-3.el6_1.1

red hat advisories RHSA-2011:1084

  • 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-2011-2696 updated cvss 4.3

libsndfile: Application crash due integer overflow by processing certain PAF audio files

  • Red Hat Enterprise Linux Server (v. 6) libsndfile 1.0.20-3.el6_1.1 Red Hat Enterprise Linux Server Optional (v. 6) libsndfile 1.0.20-3.el6_1.1
    fixed: vendor fix RHSA-2011:1084

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

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

CVSS scores

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

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.