idna: punycode labels are decoded before the 63-octet length check, so a long xn-- label causes super-linear CPU use
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| benoitc | idna | unaffected |
|
||||||
| benoitc | idna | unaffected |
|
No data.
No data.
No data available yet.
Vendor Workaround
Before passing a hostname to idna, reject any domain that contains a label longer than 63 octets. The DNS limits labels to that length, so legitimate names pass unchanged, and the decoder never runs on the crafted label. The check must run before every call that reaches idna:ulabel/1, including encode/1 and to_ascii/1, because alabel/1 decodes an ASCII xn-- label before checking its length.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Inefficient Algorithmic Complexity vulnerability in benoitc idna allows an attacker who controls a hostname passed to the library to exhaust CPU via an over-long xn-- label. idna:ulabel/1 in src/idna.erl hands every ASCII label that starts with xn-- to punycode:decode/1 without applying check_label_length/1, the 63-octet DNS label limit. punycode:decode/1 in src/punycode.erl builds its output with list appends in insert/4, so its cost grows super-linearly with the label length. A label of a few kilobytes keeps a scheduler busy for seconds to minutes before the label is rejected as invalid punycode. Every decode entry point reaches this path: decode/1, decode/2, to_unicode/1 and from_ascii/1. The encode path reaches it as well, because alabel/1 calls ulabel/1 on an ASCII xn-- label before its own length check, so encode/1, encode/2 and to_ascii/1 are affected for such input. This issue affects idna: from 0.5.0 before 8.0.0. | |
| Title | idna: punycode labels are decoded before the 63-octet length check, so a long xn-- label causes super-linear CPU use | |
| First Time appeared |
Benoitc
Benoitc idna |
|
| Weaknesses | CWE-407 | |
| CPEs | cpe:2.3:a:benoitc:idna:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Benoitc
Benoitc idna |
|
| References |
|
|
| Metrics |
cvssV4_0
|
Inefficient Algorithmic Complexity
No data.
No data.
No data.
No data.