cleo Table.set_rows 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.
5.7$0-$5k0.00

Summaryinfo

A vulnerability was found in cleo. It has been declared as critical. The impacted element is the function Table.set_rows. Executing a manipulation can lead to incorrect regex. This vulnerability is tracked as CVE-2022-42966. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability was found in cleo (version now known). It has been declared as problematic. This vulnerability affects the function Table.set_rows. The manipulation with an unknown input leads to a incorrect regex vulnerability. The CWE definition for the vulnerability is CWE-185. The product specifies a regular expression in a way that causes data to be improperly matched or compared. As an impact it is known to affect availability. CVE summarizes:

An exponential ReDoS (Regular Expression Denial of Service) can be triggered in the cleo PyPI package, when an attacker is able to supply arbitrary input to the Table.set_rows method

The weakness was disclosed 11/10/2022. The advisory is shared for download at research.jfrog.com. This vulnerability was named CVE-2022-42966 since 10/15/2022. There are known technical details, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.7

VulDB Base Score: 3.7
VulDB Temp Score: 3.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CNA Base Score: 5.9
CNA Vector (JFrog): 🔍

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: 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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

10/15/2022 🔍
11/10/2022 +26 days 🔍
11/10/2022 +0 days 🔍
12/11/2022 +31 days 🔍

Sourcesinfo

Advisory: research.jfrog.com
Status: Not defined

CVE: CVE-2022-42966 (🔍)
GCVE (CVE): GCVE-0-2022-42966
GCVE (VulDB): GCVE-100-213352

Entryinfo

Created: 11/10/2022 01:04
Updated: 12/11/2022 13:23
Changes: 11/10/2022 01:04 (36), 12/11/2022 13:23 (22)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

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!