handlebars up to 4.4.4 Regular Expression 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.
4.7$0-$5k0.00

Summaryinfo

A vulnerability was found in handlebars up to 4.4.4. It has been classified as problematic. The affected element is an unknown function of the component Regular Expression. Performing a manipulation results in incorrect regex. This vulnerability is cataloged as CVE-2019-20922. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in handlebars up to 4.4.4. It has been classified as problematic. This affects an unknown code block of the component Regular Expression. 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 summary by CVE is:

Handlebars before 4.4.5 allows Regular Expression Denial of Service (ReDoS) because of eager matching. The parser may be forced into an endless loop while processing crafted templates. This may allow attackers to exhaust system resources.

The weakness was shared 09/30/2020 (GitHub Repository). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2019-20922 since 09/30/2020. Neither technical details nor an exploit are publicly available.

Upgrading to version 4.4.5 eliminates this vulnerability.

The entry VDB-162067 is related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.2

VulDB Base Score: 3.3
VulDB Temp Score: 2.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

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: Partially
Local: Yes
Remote: Yes

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: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: handlebars 4.4.5

Timelineinfo

09/30/2020 🔍
09/30/2020 +0 days 🔍
10/01/2020 +1 days 🔍
11/14/2020 +44 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined

CVE: CVE-2019-20922 (🔍)
GCVE (CVE): GCVE-0-2019-20922
GCVE (VulDB): GCVE-100-162069
See also: 🔍

Entryinfo

Created: 10/01/2020 08:37
Updated: 11/14/2020 21:15
Changes: 10/01/2020 08:37 (38), 10/01/2020 08:42 (3), 11/13/2020 07:59 (3), 11/14/2020 21:15 (8)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!