CPU denial of service via quadratic IDNA decoding
Published Nov 9, 2022 · Updated Nov 3, 2025
Python before 3.11.1 allows remote attackers to cause CPU denial of service via crafted oversized IDNA hostnames. The IDNA decoder applies a quadratic-time path before enforcing hostname-label limits, so an extremely long attacker-controlled name consumes excessive CPU during decoding. The attack requires a client to process attacker-supplied host data, such as a redirect Location header; impact is service interruption through CPU exhaustion, without reported confidentiality or integrity effects.
Summary
What happened
Python before 3.11.1 allows remote attackers to cause CPU denial of service via crafted oversized IDNA hostnames. The IDNA decoder applies a quadratic-time path before enforcing hostname-label limits, so an extremely long attacker-controlled name consumes excessive CPU during decoding. The attack requires a client to process attacker-supplied host data, such as a redirect Location header; impact is service interruption through CPU exhaustion, without reported confidentiality or integrity effects.
The record
- CVE
- CVE-2022-45061
- Published
- Nov 9, 2022
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 9, 2022CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo