CVE-2006-0528 json
The cairo library (libcairo), as used in GNOME Evolution and possibly other products, allows remote attackers to cause a denial of service…
published 2006-02-02 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-0535
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.0%
- EPSS 11.0% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
The cairo library (libcairo), as used in GNOME Evolution and possibly other products, allows remote attackers to cause a denial of service (persistent client crash) via an attached text file that contains "Content-Disposition: inline" in the header, and a very long line in the body, which causes the client to repeatedly crash until the e-mail message is manually removed, possibly due to a buffer overflow, as demonstrated using an XML attachment.
Patch / fix
- evolution Debian 14, Debian 13, Debian 12 2.2.3-4
debian advisories DEBIAN-CVE-2006-0528
Timeline
- First public exploit (EDB-27145)
- Published
Exploit prediction
11.01% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-27145 GNOME Evolution 2.2.3/2.3.x - Inline XML File Attachment Buffer Overflow dos, 2006-01-28
- securityfocus.com http://www.securityfocus.com/bid/16408 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
References
-
securityfocus.com
/bid/16408
vdb-entry, exploit
-
usn.ubuntu.com
/265-1/
vendor-advisory
-
novell.com
/linux/security/advisories/2006_07_sr.html
vendor-advisory
-
mandriva.com
/security/advisories?name=MDKSA-2006:057
vendor-advisory
-
secunia.com
/advisories/19504
third-party-advisory, vendor-advisory
-
securityreason.com
/securityalert/610
third-party-advisory
-
archives.neohapsis.com
/archives/fulldisclosure/2006-01/0925.html
mailing-list
Sources
- CVE List CVE-2006-0528
- NVD CVE-2006-0528
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.