CVE-2007-2884 in the critical feed json
Multiple stack-based buffer overflows in Microsoft Visual Basic 6 allow user-assisted remote attackers to cause a denial of service (CPU co…
published 2007-05-30 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-2876
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 36.2%
- EPSS 36.2% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Exploit-DB
Summary
Multiple stack-based buffer overflows in Microsoft Visual Basic 6 allow user-assisted remote attackers to cause a denial of service (CPU consumption) or execute arbitrary code via a Visual Basic Project (vbp) file with a long (1) Description or (2) Company Name (VersionCompanyName) field.
Timeline
- First public exploit (EDB-3977)
- Published
Exploit prediction
36.22% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-3977 Microsoft Visual Basic 6.0 Project - Description Stack Overflow (PoC) dos, 2007-05-23
- EDB-3976 Microsoft Visual Basic 6.0 Project - Company Name Stack Overflow (PoC) dos, 2007-05-23
- securityfocus.com http://www.securityfocus.com/bid/24128 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/24129 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
References
-
exploit-db.com
/exploits/3977
exploit
-
exploit-db.com
/exploits/3976
exploit
-
securityfocus.com
/bid/24128
vdb-entry, exploit
-
securityfocus.com
/bid/24129
vdb-entry, exploit
-
osvdb.org
/41053
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/34475
vdb-entry
-
osvdb.org
/41052
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/34476
vdb-entry
Sources
- CVE List CVE-2007-2884
- NVD CVE-2007-2884
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.