Summary
Description:
A regular expression denial of service (ReDoS) vulnerability has been discovered in ua-parser-js.
Affected Versions:
From version 0.7.30 to before versions 0.7.33 / 1.0.33.
References:
Regular expression Denial of Service - ReDoS
Credits:
Thanks to @Snyk who first reported the issue.
Impact
This vulnerability bypass the library's MAX_LENGTH input limit prevention. By crafting a very-very-long user-agent string with specific pattern, an attacker can turn the script to get stuck processing for a very long time which results in a denial of service (DoS) condition.
Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.
CVE-2022-25927 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.0.33, 0.7.33); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
A patch has been released to remove the vulnerable regular expression, update to version 0.7.33 / 1.0.33 or later.
Frequently Asked Questions
- What is CVE-2022-25927? CVE-2022-25927 is a high-severity uncontrolled resource consumption vulnerability in ua-parser-js (npm), affecting versions >= 0.8.0, < 1.0.33. It is fixed in 1.0.33, 0.7.33. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
- How severe is CVE-2022-25927? CVE-2022-25927 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of ua-parser-js are affected by CVE-2022-25927? ua-parser-js (npm) versions >= 0.8.0, < 1.0.33 is affected.
- Is there a fix for CVE-2022-25927? Yes. CVE-2022-25927 is fixed in 1.0.33, 0.7.33. Upgrade to this version or later.
- Is CVE-2022-25927 exploitable, and should I be worried? Whether CVE-2022-25927 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-25927 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-25927?
- Upgrade
ua-parser-jsto 1.0.33 or later - Upgrade
ua-parser-jsto 0.7.33 or later
- Upgrade