CVE-2009-4656 in the critical feed json
Stack-based buffer overflow in E-Soft DJ Studio Pro 4.2 including 4.2.2.7.5, and 5.x including 5.1.4.3.1, allows user-assisted remote attac…
published 2010-03-03 16 y ago modified 2026-06-16 4 mo ago also EUVD-2009-4621
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 31.6%
- EPSS 31.6% chance of exploitation in 30 days, percentile 98%
- public exploits
- 5
- Metasploit, Exploit-DB
Summary
Stack-based buffer overflow in E-Soft DJ Studio Pro 4.2 including 4.2.2.7.5, and 5.x including 5.1.4.3.1, allows user-assisted remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a playlist file (.pls) containing a long string. NOTE: some of these details are obtained from third party information.
Timeline
- First public exploit (EDB-9691)
- Published
Exploit prediction
31.62% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/fileformat/djstudio_pls_bof DJ Studio Pro 5.1 .pls Stack Buffer Overflow metasploit exploit, normal rank, 2009-12-30
- EDB-18547 DJ Studio Pro 5.1 - '.pls' Local Stack Buffer Overflow (Metasploit) local, 2012-03-02
- EDB-18501 DJ Studio Pro 5.1.6.5.2 - Local Overflow (SEH) (Metasploit) local, 2012-02-20
- EDB-10827 DJ Studio Pro 5.1.6.5.2 - Local Overflow (SEH) local, 2009-12-30
- EDB-9691 DJ Studio Pro 4.2 - '.pls' Local Crash dos, 2009-09-15
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
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
exploit-db.com
/exploits/9691
exploit
-
vupen.com
/english/advisories/2009/2681
vdb-entry, vendor-advisory
-
secunia.com
/advisories/36728
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/53310
vdb-entry
Sources
- CVE List CVE-2009-4656
- NVD CVE-2009-4656
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.