jkroso parse-duration up to 2.1.2 Unicode Character redos

Summaryinfo

A vulnerability labeled as problematic has been found in jkroso parse-duration up to 2.1.2. Impacted is an unknown function of the component Unicode Character Handler. Executing a manipulation can lead to redos. The identification of this vulnerability is CVE-2025-25283. The attack may be launched remotely. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability has been found in jkroso parse-duration up to 2.1.2 and classified as problematic. This vulnerability affects an unknown part of the component Unicode Character Handler. The manipulation with an unknown input leads to a redos vulnerability. The CWE definition for the vulnerability is CWE-1333. The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. As an impact it is known to affect availability. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability was named CVE-2025-25283 since 02/06/2025. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1449.003.

Upgrading to version 2.1.3 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 9e88421bfd41806fa4b473bfb28a9ee9dafc27d7 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• jkroso

Name

• parse-duration

Version

• 2.1.0
• 2.1.1
• 2.1.2

License

• open-source

Website

• Product: https://github.com/jkroso/parse-duration/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion