ua-parser-js up to 0.7.22 incorrect regex

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.4$0-$5k0.00

Summaryinfo

A vulnerability classified as critical was found in ua-parser-js up to 0.7.22. Affected by this issue is some unknown functionality. The manipulation results in incorrect regex. This vulnerability was named CVE-2020-7793. There is no available exploit. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability classified as problematic has been found in ua-parser-js up to 0.7.22. Affected is an unknown function. The manipulation with an unknown input leads to a incorrect regex vulnerability. CWE is classifying the issue as CWE-185. The product specifies a regular expression in a way that causes data to be improperly matched or compared. This is going to have an impact on availability.

The weakness was presented 12/11/2020 as SNYK-JS-UAPARSERJS-1023599. The advisory is shared for download at snyk.io. This vulnerability is traded as CVE-2020-7793. There are neither technical details nor an exploit publicly available.

Upgrading to version 0.7.23 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be patching the affected component.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.5
VulDB Meta Temp Score: 3.4

VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Incorrect regex
CWE: CWE-185 / CWE-697
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Upgrade: ua-parser-js 0.7.23
Patch: github.com

Timelineinfo

01/21/2020 🔍
12/11/2020 +325 days 🔍
12/11/2020 +0 days 🔍
12/16/2020 +5 days 🔍

Sourcesinfo

Advisory: SNYK-JS-UAPARSERJS-1023599
Status: Confirmed

CVE: CVE-2020-7793 (🔍)
GCVE (CVE): GCVE-0-2020-7793
GCVE (VulDB): GCVE-100-166068

Entryinfo

Created: 12/11/2020 20:07
Updated: 12/16/2020 11:18
Changes: 12/11/2020 20:07 (38), 12/16/2020 11:15 (5), 12/16/2020 11:18 (1)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!