CVE-2025-15649: IO::Uncompress::Unzip versions before 2.215 for Perl propagate uncaught exception when parsing zip header with malformed DOS date
IO::Uncompress::Unzip versions before 2.215 for Perl propagate uncaught exception when parsing zip header with malformed DOS date.
_dosToUnixTime() decodes the local-file-header last-modification date field and calls Time::Local::timelocal() without an eval guard. A header whose date field decodes to an out-of-range month, day, or hour causes timelocal() to die.
The exception propagates out of IO::Uncompress::Unzip->new($file) where callers expect undef plus $UnzipError.
Security readout for executives and security teams
This flaw can crash Perl software that opens a specially malformed ZIP file through IO::Uncompress::Unzip before version 2.215. It is primarily an availability risk, not a data theft or code execution issue. Business urgency depends on whether affected Perl code processes ZIP files from users, partners, or automated ingestion pipelines. Exposure is most likely in Perl applications, batch jobs, or services using IO-Compress / IO::Uncompress::Unzip before 2.215 to parse ZIP files. Risk is higher when archives come from untrusted users, external partners, shared directories, or automated file intake. Treat this as a targeted availability fix. It should be scheduled promptly for file-processing systems, especially upload and ingestion paths, but it is not supported by sources as a breach-enabling or actively exploited vulnerability. Mitigation focus: Upgrade IO-Compress / IO::Uncompress::Unzip to version 2.215 or later.; Prioritize systems that parse ZIP files from users, partners, or automated intake paths.; If upgrading is delayed, restrict untrusted ZIP processing in affected Perl workflows..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-248: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-248 · source CWE mapping
Uncaught Exception
Uncaught Exception represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.