CVE-2024-21503: Versions of the package black before 24.3.0 are vulnerable to Regular Expression Denial of Service (ReDoS) via the…
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.97% (FIRST EPSS); higher than 62.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: n/a black 24.3.0.
Low priority for now. Upgrade to n/a black 24.3.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Versions of the package black before 24.3.0 are vulnerable to Regular Expression Denial of Service (ReDoS) via the lines_with_leading_tabs_expanded function in the strings.py file. An attacker could exploit this vulnerability by crafting a malicious input that causes a denial of service. Exploiting this vulnerability is possible when running Black on untrusted input, or if you habitually put thousands of leading tab characters in your docstrings.
- Published
- Mar 19, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.9% · 62th percentile
- CWE
- CWE-1333
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · snyk
- 5.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:P
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| python software foundation | black | cpe:2.3:a:python_software_foundation:black |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (snyk). Independent of NVD's CPE analysis and usually ahead of it.
n/a black
- before 24.3.0affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.19 | black | before 23.12.0-r0 | 23.12.0-r0 |
| Alpine:v3.20 | black | before 24.3.0-r0 | 24.3.0-r0 |
| Debian:12 | black | from 0 | — |
| Debian:13 | black | before 24.4.0-1 | 24.4.0-1 |
| openSUSE:Leap 15.6 | python-black | before 24.3.0-150400.9.8.1 | 24.3.0-150400.9.8.1 |
| openSUSE:Tumbleweed | python-black | before 26.5.1-1.3 | 26.5.1-1.3 |
| PyPI | black | before 24.3.0 | 24.3.0 |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-black | before 0:22.8.0-2.el8ap | 0:22.8.0-2.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-cryptography | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-cryptography-debuginfo | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-idna | before 0:3.7-1.el8ap | 0:3.7-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-jinja2 | before 0:3.1.4-1.el8ap | 0:3.1.4-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python39-requests | before 0:2.32.2-1.el8ap | 0:2.32.2-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-black | before 0:22.8.0-2.el8ap | 0:22.8.0-2.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-cryptography | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-cryptography-debugsource | before 0:42.0.5-1.el8ap | 0:42.0.5-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-idna | before 0:3.7-1.el8ap | 0:3.7-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-jinja2 | before 0:3.1.4-1.el8ap | 0:3.1.4-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | python3x-requests | before 0:2.32.2-1.el8ap | 0:2.32.2-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | receptor | before 0:1.4.8-1.el8ap | 0:1.4.8-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | receptorctl | before 0:1.4.8-1.el8ap | 0:1.4.8-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-black | before 0:22.8.0-2.el9ap | 0:22.8.0-2.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-cryptography | before 0:42.0.5-1.el9ap | 0:42.0.5-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | python-cryptography-debugsource | before 0:42.0.5-1.el9ap | 0:42.0.5-1.el9ap |
+51
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| n/a black | 24.3.0 | Vendor (CNA) |
| alpine:black | 23.12.0-r0 · Alpine:v3.19 | Package registry (OSV) |
| debian:black | 24.4.0-1 · Debian:13 | Package registry (OSV) |
| opensuse:python-black | 24.3.0-150400.9.8.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| PyPI:black | 24.3.0 | Package registry (OSV) |
| red hat:automation-controller-venv-tower | 0:4.5.7-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python-cryptography | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python-cryptography-debugsource | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python3-cryptography | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python3-cryptography-debuginfo | 0:42.0.5-1.el9ap · Red Hat:ansible_automation_platform_developer:2.4::el9 | Package registry (OSV) |
| red hat:python39-cryptography | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python39-cryptography-debuginfo | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python39-pillow | 0:10.3.0-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:python3x-cryptography | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:python3x-cryptography-debugsource | 0:42.0.5-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:receptor | 0:1.4.8-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:receptorctl | 0:1.4.8-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Sajeeb LohaniBugcrowd Security Innovation Lab
Not on record for this CVE: EPSS history · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-1333 · Inefficient Regular Expression ComplexityCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.