| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Sqlalchemy mako up to 1.2.1 and classified as critical. This affects the function Lexer. Performing a manipulation results in incorrect regex.
This vulnerability is cataloged as CVE-2022-40023. There is no exploit available.
The affected component should be upgraded.
Details
A vulnerability, which was classified as problematic, was found in Sqlalchemy mako up to 1.2.1. This affects the function Lexer. 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:
Sqlalchemy mako before 1.2.2 is vulnerable to Regular expression Denial of Service when using the Lexer class to parse. This also affects babelplugin and linguaplugin.
The weakness was shared 09/07/2022 as 366. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2022-40023 since 09/06/2022. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 239800 (TencentOS Server 3: python-mako (TSSA-2023:0137)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 1.2.2 eliminates this vulnerability. Applying the patch 925760291d6efec64fda6e9dd1fd9cfbd5be068c is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (239800), EUVD (EUVD-2022-0149) and CERT Bund (WID-SEC-2023-1185). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Fedora Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- Gentoo Linux
- SUSE openSUSE
- Red Hat OpenShift
- RESF Rocky Linux
Product
Vendor
Name
Version
License
Website
- Product: https://github.com/sqlalchemy/mako/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Incorrect regexCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 239800
Nessus Name: TencentOS Server 3: python-mako (TSSA-2023:0137)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: mako 1.2.2
Patch: 925760291d6efec64fda6e9dd1fd9cfbd5be068c
Timeline
09/06/2022 🔍09/07/2022 🔍
09/07/2022 🔍
12/03/2025 🔍
Sources
Product: github.comAdvisory: 366
Status: Confirmed
CVE: CVE-2022-40023 (🔍)
GCVE (CVE): GCVE-0-2022-40023
GCVE (VulDB): GCVE-100-208029
EUVD: 🔍
CERT Bund: WID-SEC-2023-1185 - Red Hat Enterprise Linux: Mehrere Schwachstellen
Entry
Created: 09/07/2022 17:01Updated: 12/03/2025 08:34
Changes: 09/07/2022 17:01 (43), 06/20/2025 08:05 (16), 11/29/2025 21:54 (7), 12/03/2025 08:18 (1), 12/03/2025 08:34 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.