CVE-2009-1641 in the critical feed json
Multiple stack-based buffer overflows in Mini-stream Ripper 3.0.1.1 allow remote attackers to execute arbitrary code via (1) a long rtsp UR…
published 2009-05-15 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1636
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 30.9%
- EPSS 30.9% chance of exploitation in 30 days, percentile 98%
- public exploits
- 3
- Metasploit, Exploit-DB
Summary
Multiple stack-based buffer overflows in Mini-stream Ripper 3.0.1.1 allow remote attackers to execute arbitrary code via (1) a long rtsp URL in a .ram file and (2) a long string in the HREF attribute of a REF element in a .asx file.
Timeline
- First public exploit (EDB-8632)
- Published
Exploit prediction
30.92% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/windows/fileformat/shadow_stream_recorder_bof Shadow Stream Recorder 3.0.1.7 Buffer Overflow metasploit exploit, normal rank, 2010-03-29
- EDB-8632 Mini-stream Ripper 3.0.1.1 - '.asx' 'HREF' Local Buffer Overflow local, 2009-05-07
- EDB-8631 Mini-stream Ripper 3.0.1.1 - '.RAM' Local Buffer Overflow local, 2009-05-07
- securityfocus.com http://www.securityfocus.com/bid/34864 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/34860 referenced PoC, tagged "exploit" by a source, unverified
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/8632
exploit
-
exploit-db.com
/exploits/8631
exploit
-
securityfocus.com
/bid/34864
vdb-entry, exploit
-
securityfocus.com
/bid/34860
vdb-entry, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/50375
vdb-entry
Sources
- CVE List CVE-2009-1641
- NVD CVE-2009-1641
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.