{"answers":{"affected":"2 open source packages ship an affected version, including parse-duration.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25283 exists.","fix":"Upgrade parse-duration to 2.1.3 or later.","what":"CVE-2025-25283 is a high-severity denial of service vulnerability in jkroso parse-duration, published on 12 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-25283 and fix it if it is affected.\n\nWhat it is: CVE-2025-25283 is a high-severity denial of service vulnerability in jkroso parse-duration, published on 12 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25283 exists.\n\nAffected packages and fixed versions:\n- parse-duration (npm): affected all versions; fixed in 2.1.3\n- parse-duration (npm): affected all versions; fixed in 2.1.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-25283/ (Markdown: https://insights.sbomify.com/CVE-2025-25283/index.md)","id":"CVE-2025-25283","markdown":"https://insights.sbomify.com/CVE-2025-25283/index.md","name":"CVE-2025-25283","record":{"aliases":["GHSA-hcrg-fc28-fcg5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js duration parser","requires_auth":"none","summary":"Attackers can cause denial of service in Node.js applications using parse-duration by triggering excessive CPU usage and memory exhaustion via crafted input strings.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-1333","name":"Inefficient Regular Expression Complexity"}],"description":"parse-duraton is software that allows users to convert a human readable duration to milliseconds. Versions prior to 2.1.3 are vulnerable to an event loop delay due to the CPU-bound operation of resolving the provided string, from a 0.5ms and up to ~50ms per one operation, with a varying size from 0.01 MB and up to 4.3 MB respectively, and an out of memory that would crash a running Node.js application due to a string size of roughly 10 MB that utilizes unicode characters. Version 2.1.3 contains a patch.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"parse-duraton vulnerable to Regex Denial of Service that results in event loop delay and out of memory","id":"CVE-2025-25283","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"Path Traversal and Local File Read via VRT (Virtual Format) in ZOO-Project WPS Implementation","id":"CVE-2025-25284"},"packages":[{"ecosystem":"npm","fixed":["2.1.3"],"introduced":["0"],"last_affected":[],"package":"parse-duration","purl":null,"source":"GHSA-hcrg-fc28-fcg5"},{"ecosystem":"npm","fixed":["2.1.3"],"introduced":["0"],"last_affected":[],"package":"parse-duration","purl":"pkg:npm/parse-duration","source":"GHSA-hcrg-fc28-fcg5"}],"prev":{"headline":"Potential Insecure Direct Object Reference (IDOR) vulnerability in ragflow","id":"CVE-2025-25282"},"products":["parse-duration"],"published":"2025-02-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-12","vendors":["jkroso"]},"summary":"Attackers can cause denial of service in Node.js applications using parse-duration by triggering excessive CPU usage and memory exhaustion via crafted input strings.","url":"https://insights.sbomify.com/CVE-2025-25283/"}