CVE-2004-0657 json
Integer overflow in the NTP daemon (NTPd) before 4.0 causes the NTP server to return the wrong date/time offset when a client requests a da…
published 2004-07-13 22 y ago modified 2026-06-16 4 mo ago also EUVD-2004-0656
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 86%
- public exploits
- 0
- none known
Summary
Integer overflow in the NTP daemon (NTPd) before 4.0 causes the NTP server to return the wrong date/time offset when a client requests a date/time that is more than 34 years away from the server's time.
Patch / fix
- ntp ntp 4.0
- ntp Debian 11 4.0
debian advisories DEBIAN-CVE-2004-0657
- kb.cert.org/vuls/id/584606 advisory
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-0657 updated cvss 7.1
ntp: wrong date/time offset return could lead to integer overflow
-
Red Hat Enterprise Linux 5 ntp Red Hat Enterprise Linux 6 ntp, ntpdate, ntp-perl Red Hat Enterprise Linux 7 ntp, sntp, ntpdate, ntp-perlnot affected: vulnerable code not present
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
Exploit prediction
2.85% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-190 Integer Overflow or Wraparound
References
-
kb.cert.org
/vuls/id/584606
third-party-advisory, patch, us-government-resource
-
marc.info
/?l=bugtraq&m=108922292425219&w=2
vendor-advisory, mailing-list, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/15406
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2004-0657
- NVD CVE-2004-0657
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.