Skip to content
Fencer Vulns
critical 9.3

CVE-2009-0490 in the critical feed json

Stack-based buffer overflow in the String_parse::get_nonspace_quoted function in lib-src/allegro/strparse.cpp in Audacity 1.2.6 and other v…

published 2009-02-10 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0494

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
16.6%
EPSS 16.6% chance of exploitation in 30 days, percentile 97%
public exploits
3
Exploit-DB

Summary

Stack-based buffer overflow in the String_parse::get_nonspace_quoted function in lib-src/allegro/strparse.cpp in Audacity 1.2.6 and other versions before 1.3.6 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a .gro file containing a long string.

Patch / fix

  • audacityteam audacity 1.3.6
  • audacity Debian 14, Debian 13, Debian 12 1.3.6-1

debian advisories DEBIAN-CVE-2009-0490

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-2009-0490 updated

audacity: stack-based buffer overflow

  • 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-7634)
  2. Published

Exploit prediction

16.63% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-10322 Audacity 1.2.6 - '.gro' Local Buffer Overflow local, 2009-12-05
  • EDB-9501 Audacity 1.2 - '.gro' Universal Buffer Overflow (Egghunter) local, 2009-08-24
  • EDB-7634 Audacity 1.2.6 - '.gro' Local Buffer Overflow (PoC) dos, 2009-01-01

CVSS scores

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

Classification

Weakness

References

Sources

Fencer Vulns 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.