idna 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.
idna 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.
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.
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.