pygments up to 2.15.0 SmithyLexer smithy.py redos

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.4$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic was found in pygments up to 2.15.0. This vulnerability affects unknown code of the file pygments/lexers/smithy.py of the component SmithyLexer. Executing a manipulation can lead to redos. This vulnerability appears as CVE-2022-40896. There is no available exploit.

Detailsinfo

A vulnerability classified as problematic was found in pygments up to 2.15.0. This vulnerability affects an unknown function of the file pygments/lexers/smithy.py of the component SmithyLexer. The manipulation with an unknown input leads to a redos vulnerability. The CWE definition for the vulnerability is CWE-1333. The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. As an impact it is known to affect availability. CVE summarizes:

A ReDoS issue was discovered in pygments/lexers/smithy.py in pygments through 2.15.0 via SmithyLexer.

The weakness was presented 07/19/2023. The advisory is available at github.com. This vulnerability was named CVE-2022-40896 since 09/19/2022. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1449.003 by the MITRE ATT&CK project.

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

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2024-0949). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

  • Fedora Linux
  • Red Hat Enterprise Linux
  • Red Hat Satellite
  • IBM MQ

Productinfo

Name

Version

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.5
VulDB Meta Temp Score: 4.4

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

NVD Base Score: 5.5
NVD Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Redos
CWE: CWE-1333 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

09/19/2022 🔍
07/19/2023 +303 days 🔍
07/19/2023 +0 days 🔍
07/27/2025 +739 days 🔍

Sourcesinfo

Product: github.com

Advisory: github.com
Status: Not defined

CVE: CVE-2022-40896 (🔍)
GCVE (CVE): GCVE-0-2022-40896
GCVE (VulDB): GCVE-100-235018
CERT Bund: WID-SEC-2024-0949 - Red Hat Satellite: Mehrere Schwachstellen

Entryinfo

Created: 07/19/2023 18:33
Updated: 07/27/2025 07:06
Changes: 07/19/2023 18:33 (37), 08/15/2023 07:56 (11), 07/27/2025 07:06 (22)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!