idna accepts Punycode labels that do not produce any non-ASCII when decoded
cve-program · CVE-2024-12224
PublishedImproper Validation of Unsafe Equivalence in punycode by the idna crate from Servo rust-url allows an attacker to create a punycode hostname that one part of a system might treat as distinct while another part of that system would treat as equivalent to another hostname.
Read the publisher's advisoryeuvd · EUVD-2024-3478
PublishedImproper Validation of Unsafe Equivalence in punycode by the idna crate from Servo rust-url allows an attacker to create a punycode hostname that one part of a system might treat as distinct while another part of that system would treat as equivalent to another hostname.
Read the publisher's advisorynvd · CVE-2024-12224
PublishedImproper Validation of Unsafe Equivalence in punycode by the idna crate from Servo rust-url allows an attacker to create a punycode hostname that one part of a system might treat as distinct while another part of that system would treat as equivalent to another hostname.
Read the publisher's advisoryosv · GHSA-h97m-ww89-6jmq
Published`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. Concretely, `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. In 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. ## Remedy Upgrade 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.) When upgrading, please take a moment to read about [alternative Unicode back ends for `idna`](https://docs.rs/crate/idna_adapter/latest). If 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. ## Additional information This 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). ## Acknowledgements Thanks to kageshiron for recognizing the security implications of this behavior.
Read the publisher's advisoryosv · RUSTSEC-2024-0421
Published`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. Concretely, `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. In 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. ## Remedy Upgrade 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.) When upgrading, please take a moment to read about [alternative Unicode back ends for `idna`](https://docs.rs/crate/idna_adapter/latest). If 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. ## Additional information This 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). ## Acknowledgements Thanks to kageshiron for recognizing the security implications of this behavior.
Read the publisher's advisoryAffected versions, risk and source history
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2024-12224
Publishedidna accepts Punycode labels that do not produce any non-ASCII when decoded
Improper Validation of Unsafe Equivalence in punycode by the idna crate from Servo rust-url allows an attacker to create a punycode hostname that one part of a system might treat as distinct while another part of that system would treat as equivalent to another hostname.
- Source published
- 30 May 2025 01:16:47 UTC
- Source modified
- 30 May 2025 12:46:56 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 4.0 · 5.1 CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N
euvd · EUVD-2024-3478
PublishedImproper Validation of Unsafe Equivalence in punycode by the idna crate from Servo rust-url allows an attacker to create a punycode hostname that one part of a system might treat as distinct while another part of that system would treat as …
Improper Validation of Unsafe Equivalence in punycode by the idna crate from Servo rust-url allows an attacker to create a punycode hostname that one part of a system might treat as distinct while another part of that system would treat as equivalent to another hostname.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: May 30, 2025, 1:16:47 AM
dateUpdated: May 30, 2025, 12:46:56 PM
65 related source bulletins · separate from aliases
openSUSE-SU-2025:15550-1: cargo-audit-0.21.2~git0.18e58c2-2.1 on GA media
CVE-2024-12224 · CVE-2025-4574 · CVE-2025-58160
RHSA-2025:17453: Red Hat Security Advisory: firefox security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
SUSE-SU-2026:0243-1: Security update for librsvg
CVE-2024-12224
SUSE-SU-2025:3785-1: Security update for afterburn
CVE-2022-24713 · CVE-2024-12224 · CVE-2025-3416 · CVE-2025-5791
openSUSE-SU-2025:15656-1: sccache-0.12.0~1-1.1 on GA media
CVE-2024-12224
RHSA-2026:87410: Red Hat Security Advisory: RHOAI 2.25.12 - Red Hat OpenShift AI
CVE-2024-12224 · CVE-2025-14920 · CVE-2025-14921 · CVE-2025-14924 · CVE-2025-14925 · CVE-2025-14926 · CVE-2025-14927 · CVE-2025-14928 · CVE-2025-14929 · CVE-2025-14930 · CVE-2025-61726 · CVE-2025-61729 · CVE-2026-5241 · CVE-2026-5497 · CVE-2026-6734 · CVE-2026-8643 · CVE-2026-9697 · CVE-2026-11822 · CVE-2026-11824 · CVE-2026-12151 · CVE-2026-12860 · CVE-2026-15143 · CVE-2026-15574 · CVE-2026-15679 · CVE-2026-15925 · CVE-2026-16221 · CVE-2026-18427 · CVE-2026-18446 · CVE-2026-18949 · CVE-2026-19481 · CVE-2026-19484 · CVE-2026-19534 · CVE-2026-25681 · CVE-2026-25960 · CVE-2026-27136 · CVE-2026-28390 · CVE-2026-28684 · CVE-2026-31812 · CVE-2026-32283 · CVE-2026-33186 · CVE-2026-33805 · CVE-2026-33811 · CVE-2026-33814 · CVE-2026-34993 · CVE-2026-39821 · CVE-2026-39852 · CVE-2026-39892 · CVE-2026-40682 · CVE-2026-41178 · CVE-2026-42502 · CVE-2026-42561 · CVE-2026-44431 · CVE-2026-44432 · CVE-2026-44660 · CVE-2026-44705 · CVE-2026-45820 · CVE-2026-47219 · CVE-2026-48526 · CVE-2026-48710 · CVE-2026-48746 · CVE-2026-49114 · CVE-2026-49825 · CVE-2026-49855 · CVE-2026-50559 · CVE-2026-54283 · CVE-2026-54399 · CVE-2026-54428 · CVE-2026-55831 · CVE-2026-55833 · CVE-2026-56121 · CVE-2026-56746 · CVE-2026-56819 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-58059 · CVE-2026-59296 · CVE-2026-59879 · CVE-2026-59884 · CVE-2026-59885 · CVE-2026-59886 · CVE-2026-59899 · CVE-2026-62243 · CVE-2026-62384 · CVE-2026-63209 · CVE-2026-63374 · CVE-2026-65898 · CVE-2026-65918 · CVE-2026-66007 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-67312 · CVE-2026-68494 · CVE-2026-68497 · CVE-2026-68770 · CVE-2026-69097 · CVE-2026-69112 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-69243 · CVE-2026-69244 · CVE-2026-71281 · CVE-2026-73086 · CVE-2026-73088 · CVE-2026-73089 · CVE-2026-73415 · CVE-2026-73417 · CVE-2026-73502 · CVE-2026-73508 · CVE-2026-73620 · CVE-2026-73622 · CVE-2026-73623 · CVE-2026-73624 · CVE-2026-73625 · CVE-2026-73627 · CVE-2026-73646 · CVE-2026-75838 · CVE-2026-75899 · CVE-2026-75931 · CVE-2026-75975 · CVE-2026-76098 · CVE-2026-76169 · CVE-2026-76172 · CVE-2026-76222 · CVE-2026-76905 · CVE-2026-77354 · CVE-2026-77874 · CVE-2026-78676 · CVE-2026-78677 · CVE-2026-78679 · CVE-2026-78682 · CVE-2026-79674 · CVE-2026-79675 · CVE-2026-80205 · CVE-2026-81722 · CVE-2026-81724 · CVE-2026-81727 · CVE-2026-82397 · CVE-2026-82417 · CVE-2026-84292 · CVE-2026-84375 · CVE-2026-84394 · CVE-2026-84428 · CVE-2026-84445 · CVE-2026-84469 · CVE-2026-84504 · CVE-2026-84782 · CVE-2026-84961 · CVE-2026-85124 · CVE-2026-85152 · CVE-2026-85525 · CVE-2026-86049 · CVE-2026-86332 · CVE-2026-87776 · CVE-2026-87817 · CVE-2026-87819 · CVE-2026-88029 · CVE-2026-88031 · CVE-2026-89418 · CVE-2026-89425 · CVE-2026-91777 · CVE-2026-91990 · CVE-2026-92599 · CVE-2026-93599 · CVE-2026-93657 · CVE-2026-93749 · CVE-2026-96749 · CVE-2026-102831 · CVE-2026-102925 · CVE-2026-102930 · CVE-2026-102937 · CVE-2026-102938 · CVE-2026-103262 · CVE-2026-104851 · CVE-2026-105744
SUSE-SU-2025:20491-1: Security update for rust-keylime
CVE-2024-12224
openSUSE-SU-2025:15551-1: cargo-c-0.10.3~git0.ee7d7ef-4.1 on GA media
CVE-2024-12224 · CVE-2025-4574 · CVE-2025-58160
SUSE-SU-2026:20910-1: Security update for librsvg
CVE-2024-12224 · CVE-2024-43806
openSUSE-SU-2026:20396-1: Security update for librsvg
CVE-2024-12224 · CVE-2024-43806
SUSE-SU-2025:3786-1: Security update for afterburn
CVE-2022-24713 · CVE-2024-12224 · CVE-2025-3416 · CVE-2025-5791
RHSA-2025:17367: Red Hat Security Advisory: firefox security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
SUSE-SU-2025:02810-1: Security update for rust-keylime
CVE-2023-26964 · CVE-2024-12224 · CVE-2024-32650 · CVE-2024-43806 · CVE-2025-3416 · CVE-2025-58266
RHSA-2025:16108: Red Hat Security Advisory: firefox security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
RHSA-2025:17371: Red Hat Security Advisory: firefox security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
SUSE-SU-2025:03306-1: Security update for sevctl
CVE-2024-12224 · CVE-2025-3416
SUSE-SU-2025:02811-1: Security update for rust-keylime
CVE-2023-26964 · CVE-2024-12224 · CVE-2024-32650 · CVE-2024-43806 · CVE-2025-3416 · CVE-2025-58266
SUSE-SU-2025:02586-1: Security update for rav1e
CVE-2024-12224
openSUSE-SU-2026:21982-1: Security update for sccache
CVE-2024-12224 · CVE-2026-25541 · CVE-2026-25727 · CVE-2026-41676 · CVE-2026-41677 · CVE-2026-41678 · CVE-2026-41681 · CVE-2026-41898 · CVE-2026-42327 · CVE-2026-44662 · CVE-2026-45784 · CVE-2026-66746 · CVE-2026-66754 · CVE-2026-67181 · CVE-2026-67182 · CVE-2026-93599 · CVE-2026-93600 · CVE-2026-93601 · CVE-2026-93602
SUSE-SU-2025:03307-1: Security update for sevctl
CVE-2024-12224 · CVE-2025-3416
openSUSE-SU-2025:15353-1: rustup-1.28.2~0-1.1 on GA media
CVE-2024-12224
RHSA-2025:17342: Red Hat Security Advisory: thunderbird security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
RHSA-2025:17340: Red Hat Security Advisory: thunderbird security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
SUSE-SU-2025:3783-1: Security update for afterburn
CVE-2022-24713 · CVE-2024-12224 · CVE-2025-3416 · CVE-2025-5791
SUSE-SU-2025:20858-1: Security update for rust-keylime
CVE-2024-12224 · CVE-2024-43806 · CVE-2024-58266 · CVE-2025-3416 · CVE-2025-55159
SUSE-SU-2026:24014-1: Security update for rustup
CVE-2024-12224 · CVE-2025-58160 · CVE-2026-25541 · CVE-2026-25727 · CVE-2026-41676 · CVE-2026-41677 · CVE-2026-41678 · CVE-2026-41681 · CVE-2026-41898 · CVE-2026-42327 · CVE-2026-44662 · CVE-2026-45784 · CVE-2026-93599 · CVE-2026-93600 · CVE-2026-93601 · CVE-2026-93602
SUSE-SU-2026:20755-1: Security update for librsvg
CVE-2024-12224 · CVE-2024-43806
RHSA-2025:17372: Red Hat Security Advisory: firefox security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
SUSE-SU-2025:20783-1: Security update for sevctl
CVE-2024-12224 · CVE-2025-3416
RHSA-2025:17368: Red Hat Security Advisory: firefox security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
RHSA-2025:16109: Red Hat Security Advisory: firefox security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
RHSA-2025:17341: Red Hat Security Advisory: thunderbird security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
RHSA-2025:17373: Red Hat Security Advisory: firefox security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
RHSA-2025:16589: Red Hat Security Advisory: thunderbird security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
openSUSE-SU-2026:20060-1: Security update for cargo-c
CVE-2024-12224 · CVE-2025-4574 · CVE-2025-58160
RHSA-2025:17343: Red Hat Security Advisory: thunderbird security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
SUSE-SU-2026:20096-1: Security update for cargo-c
CVE-2024-12224 · CVE-2025-4574 · CVE-2025-58160
RHSA-2025:17374: Red Hat Security Advisory: firefox security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
RHSA-2025:17346: Red Hat Security Advisory: thunderbird security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
openSUSE-SU-2025:15588-1: afterburn-5.9.0.git21.a73f509-2.1 on GA media
CVE-2024-12224
SUSE-RU-2025:02204-1: Recommended update for aws-nitro-enclaves-cli
CVE-2024-12224
openSUSE-SU-2025:15294-1: keylime-ima-policy-0.2.7+70-2.1 on GA media
CVE-2024-12224 · CVE-2024-43806
SUSE-SU-2025:3784-1: Security update for afterburn
CVE-2022-24713 · CVE-2024-12224 · CVE-2025-3416 · CVE-2025-5791
SUSE-SU-2026:0620-1: Security update for snpguest
CVE-2024-12224 · CVE-2025-3416 · CVE-2026-25727
WID-SEC-W-2025-0686: IBM DataPower Gateway: Mehrere Schwachstellen
CVE-2024-11738 · CVE-2024-12224
openSUSE-SU-2025:15201-1: python311-nh3-0.2.17-2.1 on GA media
CVE-2024-12224
SUSE-RU-2025:02203-1: Recommended update for aws-nitro-enclaves-cli
CVE-2024-12224
SUSE-SU-2025:03298-1: Security update for rustup
CVE-2024-12224 · CVE-2025-3416
RHSA-2025:16156: Red Hat Security Advisory: thunderbird security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
openSUSE-SU-2025:15202-1: python311-selenium-4.25.0-5.1 on GA media
CVE-2024-12224
RHSA-2025:16260: Red Hat Security Advisory: firefox security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
SUSE-SU-2025:02809-1: Security update for rust-keylime
CVE-2023-26964 · CVE-2024-12224 · CVE-2024-32650 · CVE-2024-43806 · CVE-2025-3416 · CVE-2025-58266
RHSA-2025:17378: Red Hat Security Advisory: firefox security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
SUSE-SU-2026:22917-1: Security update for afterburn
CVE-2022-24713 · CVE-2024-12224 · CVE-2025-3416 · CVE-2025-5791 · CVE-2026-25541 · CVE-2026-41676 · CVE-2026-41677 · CVE-2026-41678 · CVE-2026-41681 · CVE-2026-41898 · CVE-2026-42327 · CVE-2026-44662 · CVE-2026-45784
SUSE-SU-2026:23071-1: Security update for afterburn
CVE-2022-24713 · CVE-2024-12224 · CVE-2025-3416 · CVE-2025-5791 · CVE-2026-25541 · CVE-2026-41676 · CVE-2026-41677 · CVE-2026-41678 · CVE-2026-41681 · CVE-2026-41898 · CVE-2026-42327 · CVE-2026-44662 · CVE-2026-45784
RHSA-2025:17345: Red Hat Security Advisory: thunderbird security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
SUSE-SU-2025:4411-1: Security update for librsvg
CVE-2024-12224 · CVE-2024-43806
RHSA-2026:42644: Red Hat Security Advisory: RHOAI 2.25.9 - Red Hat OpenShift AI
CVE-2024-12224 · CVE-2025-14920 · CVE-2025-14921 · CVE-2025-14924 · CVE-2025-14926 · CVE-2025-14927 · CVE-2025-14928 · CVE-2025-14929 · CVE-2025-14930 · CVE-2025-69227 · CVE-2025-69228 · CVE-2026-5241 · CVE-2026-8643 · CVE-2026-11816 · CVE-2026-22773 · CVE-2026-22807 · CVE-2026-23490 · CVE-2026-24486 · CVE-2026-24779 · CVE-2026-25048 · CVE-2026-25681 · CVE-2026-25960 · CVE-2026-25990 · CVE-2026-27136 · CVE-2026-27145 · CVE-2026-27893 · CVE-2026-28356 · CVE-2026-28684 · CVE-2026-32281 · CVE-2026-32283 · CVE-2026-32597 · CVE-2026-32981 · CVE-2026-33186 · CVE-2026-33236 · CVE-2026-33699 · CVE-2026-33747 · CVE-2026-33811 · CVE-2026-33814 · CVE-2026-34478 · CVE-2026-34480 · CVE-2026-34993 · CVE-2026-39820 · CVE-2026-39821 · CVE-2026-39892 · CVE-2026-42499 · CVE-2026-42504 · CVE-2026-42578 · CVE-2026-42581 · CVE-2026-42584 · CVE-2026-42587 · CVE-2026-43868 · CVE-2026-43869 · CVE-2026-44431 · CVE-2026-44432 · CVE-2026-44660 · CVE-2026-48526 · CVE-2026-48746 · CVE-2026-54293
RHSA-2025:16157: Red Hat Security Advisory: thunderbird security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
SUSE-SU-2025:02768-1: Security update for sccache
CVE-2024-12224
SUSE-SU-2025:03445-1: Security update for snpguest
CVE-2024-12224 · CVE-2025-3416
openSUSE-SU-2026:22016-1: Security update for rustup
CVE-2024-12224 · CVE-2025-58160 · CVE-2026-25541 · CVE-2026-25727 · CVE-2026-41676 · CVE-2026-41677 · CVE-2026-41678 · CVE-2026-41681 · CVE-2026-41898 · CVE-2026-42327 · CVE-2026-44662 · CVE-2026-45784 · CVE-2026-93599 · CVE-2026-93600 · CVE-2026-93601 · CVE-2026-93602
SUSE-SU-2026:23983-1: Security update for sccache
CVE-2024-12224 · CVE-2026-25541 · CVE-2026-25727 · CVE-2026-41676 · CVE-2026-41677 · CVE-2026-41678 · CVE-2026-41681 · CVE-2026-41898 · CVE-2026-42327 · CVE-2026-44662 · CVE-2026-45784 · CVE-2026-66746 · CVE-2026-66754 · CVE-2026-67181 · CVE-2026-67182 · CVE-2026-93599 · CVE-2026-93600 · CVE-2026-93601 · CVE-2026-93602
RHSA-2025:17344: Red Hat Security Advisory: thunderbird security update
CVE-2024-12224 · CVE-2025-10527 · CVE-2025-10528 · CVE-2025-10529 · CVE-2025-10532 · CVE-2025-10533 · CVE-2025-10536 · CVE-2025-10537
SUSE-SU-2025:20716-1: Security update for sevctl
CVE-2024-12224 · CVE-2025-3416
- Source published
- May 30, 2025, 1:16:47 AM (timezone not stated)
- Source modified
- May 30, 2025, 12:46:56 PM (timezone not stated)
- Saved here
- 15 Nov 2026 00:38:33 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 4.0 · 5.1 CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N
nvd · CVE-2024-12224
PublishedImproper Validation of Unsafe Equivalence in punycode by the idna crate from Servo rust-url allows an attacker to create a punycode hostname that one part of a system might treat as distinct while another part of that system would treat as …
Improper Validation of Unsafe Equivalence in punycode by the idna crate from Servo rust-url allows an attacker to create a punycode hostname that one part of a system might treat as distinct while another part of that system would treat as equivalent to another hostname.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-1289 · CWE-352
Original publisher date fields
published: 2025-05-30T02:15:19.670
lastModified: 2026-06-17T06:59:17.020
1 source CPE criteria · context only
- cpe:2.3:a:servo:idna:*:*:*:*:*:rust:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 30 May 2025 02:15:19 UTC
- Source modified
- 17 Jun 2026 06:59:17 UTC
- Saved here
- 24 Oct 2026 23:17:16 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 4.0 · [email protected] · Secondary · 5.1 CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CVSS 3.1 · [email protected] · Primary · 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
osv · GHSA-h97m-ww89-6jmq
Published`idna` accepts Punycode labels that do not produce any non-ASCII when decoded
`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. Concretely, `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. In 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. ## Remedy Upgrade 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.) When upgrading, please take a moment to read about [alternative Unicode back ends for `idna`](https://docs.rs/crate/idna_adapter/latest). If 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. ## Additional information This 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). ## Acknowledgements Thanks to kageshiron for recognizing the security implications of this behavior.
- Source published
- 9 Dec 2024 20:41:10 UTC
- Source modified
- 10 Sep 2026 03:50:21 UTC
- Saved here
- 24 Oct 2026 13:19:54 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V4 · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Publisher rating · MODERATE
osv · RUSTSEC-2024-0421
Published`idna` accepts Punycode labels that do not produce any non-ASCII when decoded
`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. Concretely, `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. In 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. ## Remedy Upgrade 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.) When upgrading, please take a moment to read about [alternative Unicode back ends for `idna`](https://docs.rs/crate/idna_adapter/latest). If 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. ## Additional information This 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). ## Acknowledgements Thanks to kageshiron for recognizing the security implications of this behavior.
- Source published
- 9 Dec 2024 12:00:00 UTC
- Source modified
- 28 Oct 2025 06:02:18 UTC
- Saved here
- 24 Oct 2026 13:19:54 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.