CVE-2009-5109 in the critical feed json
Stack-based buffer overflow in Mini-Stream Ripper 3.0.1.1 allows remote attackers to execute arbitrary code via a long entry in a .pls file.
published 14y ago modified 4mo ago also EUVD-2009-5064
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 32.5%
- EPSS 32.5% chance of exploitation in 30 days, percentile 98%
- public exploits
- 5
- Metasploit and Exploit-DB
Summary
Stack-based buffer overflow in Mini-Stream Ripper 3.0.1.1 allows remote attackers to execute arbitrary code via a long entry in a .pls file.
Is CVE-2009-5109 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit exploit/windows/misc/mini_stream)
- Published
Exploit prediction
32.46% 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/misc/mini_stream Mini-Stream 3.0.1.1 Buffer Overflow metasploit exploit, normal rank, 2009-12-25
- EDB-18082 Mini-stream Ripper 3.0.1.1 - Local Buffer Overflow (Metasploit) (3) local, 2011-11-04
- EDB-10782 Mini-stream Ripper 3.0.1.1 - '.pls' Universal Buffer Overflow local, 2009-12-29
- EDB-10747 Mini-stream Ripper (Windows XP SP2/SP3) - Local Overflow local, 2009-12-27
- EDB-10745 Mini-stream Ripper 3.0.1.1 - '.pls' Universal Local Buffer Overflow local, 2009-12-27
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/10782
exploit
-
exploit-db.com
/exploits/18082
exploit
-
exploit-db.com
/exploits/10745
exploit
-
exploit-db.com
/exploits/10747
exploit
-
osvdb.org
/61341
vdb-entry
Sources
- CVE List CVE-2009-5109
- NVD CVE-2009-5109
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.