CVE details
CVE-2022-45061
An issue was discovered in Python before 3.11.1. An unnecessary quadratic algorithm exists in one path when processing some inputs to the IDNA (RFC 3490) decoder, such that a crafted, unreasonably long name being presented to the decoder could lead to a CPU denial of service. Hostnames are often supplied by remote servers that could be controlled by a malicious actor; in such a scenario, they could trigger excessive CPU consumption on the client attempting to make use of an attacker-supplied supposed hostname. For example, the attack payload could be placed in the Location header of an HTTP response with status code 302. A fix is planned in 3.11.1, 3.10.9, 3.9.16, 3.8.16, and 3.7.16.
Affected ports (1)
| Port | Package | Version | Status | Maintainer |
|---|---|---|---|---|
| lang/python27 | python27 | 2.7.18_5 | unaddressed | python@FreeBSD.org |
Template for a VuXML entry
Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.
<vuln vid="FIXME (make newentry)">
<topic>FIXME -- FIXME</topic>
<affects>
<package>
<name>python27</name>
<range><lt>FIXME</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>An issue was discovered in Python before 3.11.1. An unnecessary
quadratic algorithm exists in one path when processing some inputs to
the IDNA (RFC 3490) decoder, such that a crafted, unreasonably long
name being presented to the decoder could lead to a CPU denial of
service. Hostnames are often supplied by remote servers that could be
controlled by a malicious actor; in such a scenario, they could
trigger excessive CPU consumption on the client attempting to make use
of an attacker-supplied supposed hostname. For example, the attack
payload could be placed in the Location header of an HTTP response
with status code 302. A fix is planned in 3.11.1, 3.10.9, 3.9.16,
3.8.16, and 3.7.16.</p>
</body>
</description>
<references>
<cvename>CVE-2022-45061</cvename>
<url>https://nvd.nist.gov/vuln/detail/CVE-2022-45061</url>
</references>
<dates>
<discovery>2022-11-09</discovery>
<entry>2026-10-25</entry>
</dates>
</vuln>