CVE-2003-0300

NONECVSS 0.0

0.0

The IMAP Client for Sylpheed 0.8.11 allows remote malicious IMAP servers to cause a denial of service (crash) via certain large literal size values that cause either integer signedness errors or integer overflow errors.

CVSS v3: —
EG Score: —
EPSS: 75.1%
KEV: Not listed

Published

June 16, 2003

Last Modified

April 16, 2026

References (2)

cve@mitrehttp://marc.info/?l=bugtraq&m=105294024124163&w=2
af854a3a-2127-422b-91ae-364da2661108http://marc.info/?l=bugtraq&m=105294024124163&w=2

Data Freshness Timeline

(refreshed 11× in last 7d / 15× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-29 13:40 UTCepss_batch
2026-05-29 13:40 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:37 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-22 21:15 UTCepss_batch
2026-05-20 11:20 UTCepss_batch
2026-05-20 11:20 UTCepss_batch
2026-05-18 21:29 UTCepss_batch
2026-05-18 21:29 UTCepss_batch

Frequently asked(4)

What is CVE-2003-0300?

CVE-2003-0300 is a none vulnerability published on June 16, 2003. The IMAP Client for Sylpheed 0.8.11 allows remote malicious IMAP servers to cause a denial of service (crash) via certain large literal size values that cause either integer signedness errors or integer overflow errors.

When was CVE-2003-0300 disclosed?

CVE-2003-0300 was first published in the National Vulnerability Database on June 16, 2003, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2003-0300 actively exploited?

CVE-2003-0300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 75.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2003-0300?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2003-0300, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2003-0300

Explore →

Is Your Infrastructure Affected by CVE-2003-0300?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2003-0300

📅 Published

🔄 Last Modified

🔗 References (2)