CVE-2018-20164

CVE-2018-20164 is a medium-severity vulnerability in Uaparser User Agent Parser-core with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-185.

Key facts

Description

An issue was discovered in regex.yaml (aka regexes.yaml) in UA-Parser UAP-Core before 0.6.0. A Regular Expression Denial of Service (ReDoS) issue allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to a value containing a long digit string. (The UAP-Core project contains the vulnerability, propagating to all implementations.)

Frequently asked questions

What is CVE-2018-20164?
An issue was discovered in regex.yaml (aka regexes.yaml) in UA-Parser UAP-Core before 0.6.0. A Regular Expression Denial of Service (ReDoS) issue allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to a value containing a long digit string. (The UAP-Core project contains the vulnerability, propagating to all implementations.)
How severe is CVE-2018-20164?
CVE-2018-20164 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability low.
Is CVE-2018-20164 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (87th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-20164?
CVE-2018-20164 affects Uaparser User Agent Parser-core. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-20164?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2018-20164 published?
CVE-2018-20164 was published on 2019-02-13 and last updated on 2026-06-17.

References

Affected products (1)

Other CWE-185 vulnerabilities

Browse all CWE-185 vulnerabilities →