Skip to content
Fencer Intel
high 7.5

CVE-2012-0270 in the critical feed json

Multiple stack-based buffer overflows in Csound before 5.16.6 allow remote attackers to execute arbitrary code via a crafted (1) hetro file…

published 2014-02-17 12 y ago modified 2026-06-16 4 mo ago also EUVD-2012-0306

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
54.7%
EPSS 54.7% chance of exploitation in 30 days, percentile 99%
public exploits
2
Metasploit, Exploit-DB

Summary

Multiple stack-based buffer overflows in Csound before 5.16.6 allow remote attackers to execute arbitrary code via a crafted (1) hetro file to the getnum function in util/heti_main.c or (2) PVOC file to the getnum function in util/pv_import.c.

Patch / fix

  • csound Debian 14, Debian 13, Debian 12 1:5.16.6~dfsg-1

debian advisories DEBIAN-CVE-2012-0270

  • csound openSUSE Tumbleweed 5.18.02-7.10

opensuse advisories openSUSE-SU-2024:10575-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-0270 updated cvss 5.1

csound: two buffer overflow flaws in getnum()

  • 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 (Metasploit exploit/windows/fileformat/csound_getnum_bof)
  2. Published

Exploit prediction

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

Exploits and checks

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/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.