CVE-2026-60074

{"id": "CVE-2026-60074", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-60074", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-07-31T17:57:22.582933Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "affected": [{"source": "9b29abf9-4ab0-4765-b253-1875cd9b441e", "affectedData": [{"repo": "https://github.com/SBECK-github/Date-Manip", "modules": ["Date::Manip"], "versions": [{"status": "affected", "version": "0", "versionType": "custom", "lessThanOrEqual": "7.00"}], "packageURL": "pkg:cpan/Date-Manip", "packageName": "Date-Manip", "programFiles": ["lib/Date/Manip/Base.pm", "lib/Date/Manip/Date.pm"], "collectionURL": "https://cpan.org/modules", "defaultStatus": "unaffected", "programRoutines": [{"name": "Date::Manip::Base::check"}, {"name": "Date::Manip::Date::_parse_check"}, {"name": "Date::Manip::Date::_iso8601_rx"}, {"name": "Date::Manip::Date::_other_rx"}, {"name": "Date::Manip::Date::parse_format"}]}]}], "published": "2026-07-30T14:17:02.587", "references": [{"url": "https://github.com/SBECK-github/Date-Manip/pull/54", "source": "9b29abf9-4ab0-4765-b253-1875cd9b441e"}, {"url": "https://metacpan.org/release/SBECK/Date-Manip-6.99/source/lib/Date/Manip/Base.pm#L602-614", "source": "9b29abf9-4ab0-4765-b253-1875cd9b441e"}, {"url": "https://metacpan.org/release/SBECK/Date-Manip-6.99/source/lib/Date/Manip/Date.pm#L1536-1539", "source": "9b29abf9-4ab0-4765-b253-1875cd9b441e"}, {"url": "https://security.metacpan.org/patches/D/Date-Manip/6.99/CVE-2026-60074-r1.patch", "source": "9b29abf9-4ab0-4765-b253-1875cd9b441e"}, {"url": "http://www.openwall.com/lists/oss-security/2026/07/30/19", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "9b29abf9-4ab0-4765-b253-1875cd9b441e", "description": [{"lang": "en", "value": "CWE-1289"}]}], "descriptions": [{"lang": "en", "value": "Date::Manip versions through 7.00 for Perl return corrupted dates via non-ASCII decimal digits that pass the numeric range tests in check.\n\nThe parse regexes capture year, month and day with the `\\d` shorthand, which on a character string matches the whole Unicode decimal digit property `\\p{Nd}` and not just `[0-9]`. Date::Manip::Base::check then validates the captured fields with numeric comparisons alone (`$y<1 || $y>9999`, `$m<1 || $m>12`, `$d<1 || $d>$days`), and _parse_check stores the numified fields (`$y+0`). Perl truncates a string at the first character that is not an ASCII digit, so a field whose leading characters are ASCII digits numifies to an in-range prefix and satisfies every test: a year field of three ASCII digits followed by U+0664 ARABIC-INDIC DIGIT FOUR numifies to 202, giving the year 0202, and one non-ASCII digit in the month or day field shifts those fields the same way. The hour, minute and second fields match explicit ASCII character classes (`0?[0-9]`, `[0-5][0-9]`) and do not shift, though a non-ASCII digit in a fractional hour or minute field truncates the fraction.\n\nAny caller that passes an untrusted character string to ParseDate() or Date::Manip::Date->parse() can get back a date that differs from the string it parsed, with no parse error. Where the parsed date gates logic such as an expiry check or a retention window, the shift goes unnoticed."}, {"lang": "es", "value": "Las versiones de Date::Manip hasta la 6.99 para Perl devuelven fechas corruptas a trav\u00e9s de d\u00edgitos decimales no ASCII que pasan las pruebas de rango num\u00e9rico en la verificaci\u00f3n.\n\nLas expresiones regulares de an\u00e1lisis capturan el a\u00f1o, el mes y el d\u00eda con la abreviatura \u201c\\d\u201d, que en una cadena de caracteres coincide con la propiedad completa de d\u00edgito decimal Unicode \u201c\\p{Nd}\u201d y no solo \u201c[0-9]\u201d. Date::Manip::Base::check luego valida los campos capturados solo con comparaciones num\u00e9ricas (\u201c$y<1 || $y>9999\u201d, \u201c$m<1 || $m>12\u201d, \u201c$d<1 || $d>$days\u201d), y _parse_check almacena los campos numificados (\u201c$y+0\u201d). Perl trunca una cadena en el primer car\u00e1cter que no es un d\u00edgito ASCII, por lo que un campo cuyos caracteres iniciales son d\u00edgitos ASCII se numifica a un prefijo dentro del rango y satisface todas las pruebas: un campo de a\u00f1o de tres d\u00edgitos ASCII seguido de U+0664 D\u00cdGITO AR\u00c1BIGO-\u00cdNDICO CUATRO se numifica a 202, dando el a\u00f1o 0202, y un d\u00edgito no ASCII en el campo del mes o del d\u00eda desplaza esos campos de la misma manera. Los campos de hora, minuto y segundo coinciden con clases de caracteres ASCII expl\u00edcitas (\u201c0?[0-9]\u201d, \u201c[0-5][0-9]\u201d) y no se desplazan, aunque un d\u00edgito no ASCII en un campo de hora o minuto fraccional trunca la fracci\u00f3n.\n\nCualquier llamador que pase una cadena de caracteres no confiable a ParseDate() o Date::Manip::Date -> parse() puede obtener una fecha que difiere de la cadena que analiz\u00f3, sin error de an\u00e1lisis. Donde la fecha analizada controla la l\u00f3gica, como una verificaci\u00f3n de caducidad o una ventana de retenci\u00f3n, el desplazamiento pasa desapercibido."}], "lastModified": "2026-10-23T22:10:00.160", "sourceIdentifier": "9b29abf9-4ab0-4765-b253-1875cd9b441e"}