CVE-2020-5243: Denial of Service in uap-core when processing crafted User-Agent strings

uap-core Updated 02 Oct 2025

Summary

20/02/2020
Yes i
Moderate
5.7

CVE-2020-5243: Denial of Service in uap-core when processing crafted User-Agent strings. Affects uap-core versions < 0.7.3. Fixed in 0.7.3. How to fix ↓

Also tracked for

The same CVE-2020-5243 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

uap-core is an npm package that provides user-agent parsing functionality. It is commonly used in web applications to extract information about the client's browser, operating system, and device. This vulnerability in uap-core allows remote attackers to perform a Denial of Service (DoS) attack by sending maliciously crafted User-Agent strings. The vulnerability arises from the presence of overlapping capture groups in certain regular expressions used by uap-core. When a long string is processed by these vulnerable regular expressions, it causes excessive backtracking, leading to a significant slowdown or crash of the server.

Vulnerability Detail

The vulnerability in uap-core arises from the presence of overlapping capture groups in certain regular expressions. This allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to maliciously crafted long strings. The backtracking required to process these strings has a cubic time complexity, making it an effective vector for a Denial of Service attack. The impact of this vulnerability can range from server slowdowns to complete unavailability, depending on the server's capacity and the size of the crafted User-Agent string.

How To Fix

Minimum fixed version

0.7.3

This is the first release that contains the fix.

npm install uap-core@0.7.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended solution is to update uap-core to the latest version.

Conclusion

The vulnerability in uap-core allows remote attackers to perform a Denial of Service attack by sending maliciously crafted User-Agent strings. To mitigate this vulnerability, it is crucial to update uap-core and any downstream packages to the latest versions that include the necessary patches. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for uap-core →

Share this vulnerability

FAQ

uap-core is an npm package that provides user-agent parsing functionality. It is commonly used in web applications to extract information about the client's browser, operating system, and device.

The vulnerability allows remote attackers to perform a Denial of Service attack by sending maliciously crafted User-Agent strings. This can lead to server slowdowns or unavailability.

To fix this vulnerability, update uap-core to version 0.7.3 or higher. Make sure to also update any downstream packages that depend on uap-core.

There are no specific workarounds mentioned for this vulnerability. Updating to the latest version is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for uap-core.

How To Fix

Minimum fixed version

0.7.3

This is the first release that contains the fix.

npm install uap-core@0.7.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback