CVE-2005-3831 json
Stack-based buffer overflow in (1) CxZIP60.dll and (2) CxZIP60u.dll, as used in SpeedProject products including (a) ZipStar 5.0 Build 4285,…
published 2005-11-26 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-3826
- cvss
- 5.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
Stack-based buffer overflow in (1) CxZIP60.dll and (2) CxZIP60u.dll, as used in SpeedProject products including (a) ZipStar 5.0 Build 4285, (b) Squeez 5.0 Build 4285, and (c) SpeedCommander 11.0 Build 4430 and 10.51 Build 4430, allows user-assisted attackers to execute arbitrary code via a ZIP archive containing a long filename.
Patch / fix
- secunia.com/secunia_research/2005-60/advisory advisory
- securitytracker.com/id?1015265 advisory
- securitytracker.com/id?1015267 advisory
- secunia.com/advisories/17420 advisory
- securitytracker.com/id?1015266 advisory
Exploit prediction
2.60% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.1 | AV:N/AC:H/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
/secunia_research/2005-60/advisory
patch, vendor-advisory
-
securitytracker.com
/id?1015265
vdb-entry, patch, vendor-advisory
-
securitytracker.com
/id?1015267
vdb-entry, patch, vendor-advisory
-
secunia.com
/advisories/17420
third-party-advisory, patch, vendor-advisory
-
securitytracker.com
/id?1015266
vdb-entry, patch, vendor-advisory
-
vupen.com
/english/advisories/2005/2570
vdb-entry, vendor-advisory
-
securityfocus.com
/archive/1/417588/30/0/threaded
mailing-list
-
osvdb.org
/21073
vdb-entry
Sources
- CVE List CVE-2005-3831
- NVD CVE-2005-3831
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.