Skip to content
Fencer Intel
medium 6.8

CVE-2012-6303 json

Heap-based buffer overflow in the GetWavHeader function in generic/jkSoundFile.c in the Snack Sound Toolkit, as used in WaveSurfer 1.8.8p4,…

published 2013-10-28 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-6158

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
10.2%
EPSS 10.2% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

Heap-based buffer overflow in the GetWavHeader function in generic/jkSoundFile.c in the Snack Sound Toolkit, as used in WaveSurfer 1.8.8p4, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a large chunk size in a WAV file.

Patch / fix

  • snack Debian 14, Debian 13, Debian 12 2.2.10-dfsg1-12.1

debian advisories DEBIAN-CVE-2012-6303

  • snack openSUSE Tumbleweed 2.2.10-215.2

opensuse advisories openSUSE-SU-2024:11390-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-2012-6303 updated cvss 2.1

tcl-snack: multiple buffer overflows

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

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

Timeline

  1. First public exploit (EDB-19772)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-19772 WaveSurfer 1.8.8p4 - Memory Corruption (PoC) dos, 2012-07-12

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.