DateTime::Lite versions before 0.8.1 for Perl allow CPU exhaustion via a per-day loop when adding seconds
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.8.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The DateTime::Lite Perl module (a lightweight date and time library) is affected, in both its XS and pure-Perl implementations. When an attacker can control the number of seconds added to a date object, the library loops once per day, so a very large value can tie up the CPU for as long as the attacker wants.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
DateTime::Lite versions before 0.8.1 for Perl allow CPU exhaustion via a per-day loop when adding seconds. _normalize_leap_seconds crosses day boundaries one day at a time, so add(seconds => $n) on an object with a non-floating time zone takes about |$n|/86400 iterations, and nothing limits $n. The XS implementation and the pure-Perl fallback both have the loop. An attacker who controls the number of seconds added can keep the process busy for as long as they choose.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- DateTime-Lite
fixed in 0.8.1