{"id":"RUSTSEC-2024-0421","revision":"b3aca4e0da1746b4a6d610fa1f0bd961","records":[{"revision":"b3aca4e0da1746b4a6d610fa1f0bd961","observedAt":"2026-10-24T13:19:54.901+00:00","statement":{"source":"osv","id":"RUSTSEC-2024-0421","aliases":["CVE-2024-12224","GHSA-h97m-ww89-6jmq"],"title":"`idna` accepts Punycode labels that do not produce any non-ASCII when decoded","description":"`idna` 0.5.0 and earlier accepts Punycode labels that do not produce any non-ASCII output, which means that either ASCII labels or the empty root label can be masked such that they appear unequal without IDNA processing or when processed with a different implementation and equal when processed with `idna` 0.5.0 or earlier.\n\nConcretely, `example.org` and `xn--example-.org` become equal after processing by `idna` 0.5.0 or earlier. Also, `example.org.xn--` and `example.org.` become equal after processing by `idna` 0.5.0 or earlier.\n\nIn applications using `idna` (but not in `idna` itself) this may be able to lead to privilege escalation when host name comparison is part of a privilege check and the behavior is combined with a client that resolves domains with such labels instead of treating them as errors that preclude DNS resolution / URL fetching and with the attacker managing to introduce a DNS entry (and TLS certificate) for an `xn--`-masked name that turns into the name of the target when processed by `idna` 0.5.0 or earlier.\n\n## Remedy\n\nUpgrade to `idna` 1.0.3 or later, if depending on `idna` directly, or to `url` 2.5.4 or later, if depending on `idna` via `url`. (This issue was fixed in `idna` 1.0.0, but versions earlier than 1.0.3 are not recommended for other reasons.)\n\nWhen upgrading, please take a moment to read about [alternative Unicode back ends for `idna`](https://docs.rs/crate/idna_adapter/latest).\n\nIf you are using Rust earlier than 1.81 in combination with SQLx 0.8.2 or earlier, please also read an [issue](https://github.com/servo/rust-url/issues/992) about combining them with `url` 2.5.4 and `idna` 1.0.3.\n\n## Additional information\n\nThis issue resulted from `idna` 0.5.0 and earlier implementing the UTS 46 specification literally on this point and the specification having this bug. The specification bug has been fixed in [revision 33 of UTS 46](https://www.unicode.org/reports/tr46/tr46-33.html#Modifications).\n\n## Acknowledgements\n\nThanks to kageshiron for recognizing the security implications of this behavior.","state":0,"publishedAt":"2024-12-09T12:00:00+00:00","modifiedAt":"2025-10-28T06:02:18+00:00","affected":[{"ecosystem":"crates.io","name":"idna","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0.0.0-0"},{"kind":"fixed","version":"1.0.0"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[],"references":["https://crates.io/crates/idna","https://rustsec.org/advisories/RUSTSEC-2024-0421.html","https://bugzilla.mozilla.org/show_bug.cgi?id=1887898"],"sourceUrl":"https://osv.dev/vulnerability/RUSTSEC-2024-0421","license":"OSV · upstream source license applies","key":"osv:RUSTSEC-2024-0421","identifiers":["RUSTSEC-2024-0421","CVE-2024-12224","GHSA-h97m-ww89-6jmq"]},"retained":false,"historicalAffected":[]}],"coverage":[]}