CVE-2003-0328 json
EPIC IRC Client (EPIC4) pre2.002, pre2.003, and possibly later versions, allows remote malicious IRC servers to cause a denial of service (…
published 2003-05-22 23 y ago modified 2026-06-16 4 mo ago also EUVD-2003-0323
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 8.6%
- EPSS 8.6% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
EPIC IRC Client (EPIC4) pre2.002, pre2.003, and possibly later versions, allows remote malicious IRC servers to cause a denial of service (crash) and possibly execute arbitrary code via a CTCP request from a large nickname, which causes an incorrect length calculation.
Patch / fix
- epic4 Debian 14, Debian 13, Debian 12 1:1.1.11.20030409-2
debian advisories DEBIAN-CVE-2003-0328
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2003-0328 updated
security flaw
-
Red Hat Linux 7.3 Red Hat Linux 8.0 Red Hat Linux 9fixed: vendor fix RHSA-2003:342
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Timeline
- Published
- First public exploit (EDB-23366)
Exploit prediction
8.62% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-23366 Epic 1.0.1/1.0.x - CTCP Nickname Server Message Buffer Overrun remote, 2003-11-10
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
References
-
debian.org
/security/2003/dsa-399
vendor-advisory
-
debian.org
/security/2003/dsa-306
vendor-advisory
-
redhat.com
/support/errata/RHSA-2003-342.html
vendor-advisory
Sources
- CVE List CVE-2003-0328
- NVD CVE-2003-0328
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.