Skip to content
Fencer Vulns
high 7.5

CVE-2004-0396 in the critical feed json

Heap-based buffer overflow in CVS 1.11.x up to 1.11.15, and 1.12.x up to 1.12.7, when using the pserver mechanism allows remote attackers t…

published 2004-05-20 22 y ago modified 2026-06-16 4 mo ago also EUVD-2004-0396

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
67.5%
EPSS 67.5% chance of exploitation in 30 days, percentile 99.3%
public exploits
2
Exploit-DB

Summary

Heap-based buffer overflow in CVS 1.11.x up to 1.11.15, and 1.12.x up to 1.12.7, when using the pserver mechanism allows remote attackers to execute arbitrary code via Entry lines.

Patch / fix

  • cvs Debian 14, Debian 13, Debian 12 1:1.12.5-6

debian advisories DEBIAN-CVE-2004-0396

  • cvs RHEL 3 1.11.2-22

red hat advisories RHSA-2004:190

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-2004-0396 updated

security flaw

  • Red Hat Desktop version 3 cvs 1.11.2-22 Red Hat Enterprise Linux AS version 3 cvs 1.11.2-22 Red Hat Enterprise Linux ES version 3 cvs 1.11.2-22 Red Hat Enterprise Linux WS version 3 cvs 1.11.2-22
    fixed: vendor fix RHSA-2004:190

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

  1. Published
  2. First public exploit (EDB-301)

Exploit prediction

67.53% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-301 CVS - Remote Entry Line Root Heap Overflow remote, 2004-06-25
  • EDB-300 CVS (Linux/FreeBSD) - Remote Entry Line Heap Overflow remote, 2004-06-25

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

Sources

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.