CVE-2009-0184 in the critical feed json
Multiple buffer overflows in the torrent parsing implementation in Free Download Manager (FDM) 2.5 Build 758 and 3.0 Build 844 allow remote…
published 2009-02-03 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-0193
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 27.8%
- EPSS 27.8% chance of exploitation in 30 days, percentile 98%
- public exploits
- 3
- Metasploit, Exploit-DB
Summary
Multiple buffer overflows in the torrent parsing implementation in Free Download Manager (FDM) 2.5 Build 758 and 3.0 Build 844 allow remote attackers to execute arbitrary code via (1) a long file name within a torrent file, (2) a long tracker URL in a torrent file, or (3) a long comment in a torrent file.
Timeline
- First public exploit (Metasploit exploit/windows/fileformat/fdm_torrent)
- Published
Exploit prediction
27.80% 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/fdm_torrent Free Download Manager Torrent Parsing Buffer Overflow metasploit exploit, good rank, 2009-02-02
- EDB-16634 Free Download Manager 3.0 Build 844 - Torrent Parsing Buffer Overflow (Metasploit) local, 2010-09-25
- EDB-10009 Free Download Manager - '.Torrent' File Parsing Multiple Buffer Overflow Vulnerabilities (Metasploit) local, 2009-11-11
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
-
secunia.com
/advisories/33524
third-party-advisory, vendor-advisory
-
secunia.com
/secunia_research/2009-5/
vendor-advisory
-
securityfocus.com
/bid/33555
vdb-entry
-
securityfocus.com
/archive/1/500605/100/0/threaded
mailing-list
-
vupen.com
/english/advisories/2009/0302
vdb-entry
Sources
- CVE List CVE-2009-0184
- NVD CVE-2009-0184
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.