A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://python-security.readthedocs.io/vuln/slow-idna-large-strings.html below:

Slow IDNA decoding with large strings — Python Security 0.0 documentation

Slow IDNA decoding with large strings

IDNA decoding execution time is not linear in relation to the input string size, which can cause slowness with large inputs:

According to Unicode Technical Standard #46, an IDNA label must not be longer than 63 characters. The Python idna module enforces the restriction, but too late.

Dates:

Fixed In Python issue

Slow IDNA decoding with large strings [CVE-2022-45061].

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.

Timeline

Timeline using the disclosure date 2022-10-19 as reference:


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4