CVE-2007-5217 json
Stack-based buffer overflow in the ADM4 ActiveX control in adm4.dll in Altnet Download Manager 4.0.0.6, as used in (1) Kazaa 3.2.7 and (2)…
published 2007-10-05 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-5197
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 30.0%
- EPSS 30.0% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
Stack-based buffer overflow in the ADM4 ActiveX control in adm4.dll in Altnet Download Manager 4.0.0.6, as used in (1) Kazaa 3.2.7 and (2) Grokster, allows remote attackers to execute arbitrary code via a long argument to the Install method. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
Timeline
- First public exploit (Metasploit exploit/windows/browser/kazaa_altnet_heap)
- Published
Exploit prediction
29.99% 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/browser/kazaa_altnet_heap Kazaa Altnet Download Manager ActiveX Control Buffer Overflow metasploit exploit, normal rank, 2007-10-03
- EDB-16496 Kazaa Altnet Download Manager - ActiveX Control Buffer Overflow (Metasploit) remote, 2010-05-09
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
secunia.com
/advisories/26972
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/26970
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/36929
vdb-entry
-
securityfocus.com
/bid/25903
vdb-entry
-
vupen.com
/english/advisories/2007/3336
vdb-entry
-
vupen.com
/english/advisories/2007/3335
vdb-entry
-
osvdb.org
/37785
vdb-entry
-
osvdb.org
/38435
vdb-entry
Sources
- CVE List CVE-2007-5217
- NVD CVE-2007-5217
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.