CVE-2005-3354 json
Stack-based buffer overflow in the ldif_get_line function in ldif.c of Sylpheed before 2.1.6 allows user-assisted attackers to execute arbi…
published 2005-11-20 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-3353
- cvss
- 5.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.8%
- EPSS 3.8% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
Stack-based buffer overflow in the ldif_get_line function in ldif.c of Sylpheed before 2.1.6 allows user-assisted attackers to execute arbitrary code by having local users import LDIF files with long lines.
Patch / fix
- sylpheed Debian 13, Debian 12 2.0.4-1
debian advisories DEBIAN-CVE-2005-3354
Exploit prediction
3.79% chance of exploitation in the next 30 days, higher than 90% 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
-
gentoo.org
/security/en/glsa/glsa-200511-13.xml
vendor-advisory, patch
-
novell.com
/linux/security/advisories/2005_28_sr.html
vendor-advisory
-
debian.org
/security/2005/dsa-906
vendor-advisory
-
xatrix.org
/advisory.php?s=7282
vendor-advisory
-
secunia.com
/advisories/17492
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/17831/
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2005/2360
vdb-entry, vendor-advisory
-
secunia.com
/advisories/17678
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/17540/
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/17525/
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/15363
vdb-entry
- sylpheed.good-day.net /en/news.html
-
exchange.xforce.ibmcloud.com
/vulnerabilities/23028
vdb-entry
-
osvdb.org
/20675
vdb-entry
Sources
- CVE List CVE-2005-3354
- NVD CVE-2005-3354
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.