Technical impact
The vulnerability arises when DateTime::Lite uses a per‑day loop to normalize leap seconds. The add(seconds => $n) routine iterates once for every 86,400 seconds in the value of $n, and the routine has no upper bound. An attacker who can influence the seconds value can therefore cause the module to run for an arbitrarily long time, exhausting CPU resources. The result is a denial‑of‑service condition, where legitimate processes or the host system may become unresponsive.
Affected Systems
Perl applications that depend on the DateTime::Lite CPAN module with a version earlier than 0.8.1 are vulnerable. The vulnerability is present in all pre‑0.8.1 releases run with the XS implementation and the pure‑Perl fallback.
Risk and Exploitability
Because the loop has no built‑in rate limiting, the condition can be triggered with a single call that supplies a large seconds argument. There's no network or remote trigger described, so exploitation requires control of the add(seconds) parameter from within the application. The CVSS score of 7.5 indicates a high severity flaw, and the EPSS score of less than 1% denotes a low probability of exploitation. The lack of a defensive guard makes the flaw a high‑impact denial‑of‑service vector. The vulnerability is not currently listed in the CISA KEV catalog.