https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 05:33:29 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-13518 bdu:2025-13518 https://cve.radiocsirt.org/vuln/bdu:2025-13518 https://cve.radiocsirt.org/vuln/euvd-2026-241991 EUVD-2026-241991 https://cve.radiocsirt.org/vuln/euvd-2026-241991 https://cve.radiocsirt.org/vuln/fkie_cve-2024-12224 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-12224 https://cve.radiocsirt.org/vuln/ghsa-h97m-ww89-6jmq <p><strong>Affected:</strong> crates.io: idna</p> <p>`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.</p> <p>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.</p> <p>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.</p> <p>## Remedy</p> <p>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.)</p> <p>When upgrading, please take a moment to read about [alternative Unicode back ends for `idna`](https://docs.rs/crate/idna_adapter/latest).</p> <p>If you are using Rust earlier than 1.81 in combination with SQLx…</p> <p><strong>Affected:</strong> crates.io: idna</p> <p>`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.</p> <p>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.</p> <p>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.</p> <p>## Remedy</p> <p>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.)</p> <p>When upgrading, please take a moment to read about [alternative Unicode back ends for `idna`](https://docs.rs/crate/idna_adapter/latest).</p> <p>If you are using Rust earlier than 1.81 in combination with SQLx…</p> https://cve.radiocsirt.org/vuln/ghsa-h97m-ww89-6jmq https://cve.radiocsirt.org/vuln/oesa-2026-2944 <p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: rpm-ostree</p> <p>rpm-ostree is a hybrid image/package system. It supports &amp;amp;quot;composing&amp;amp;quot; packages on a build server into an OSTree repository, which can then be replicated by client systems with atomic upgrades. Additionally, unlike many &amp;amp;quot;pure&amp;amp;quot; image systems, with rpm-ostree each client system can layer on additional packages, providing a &amp;amp;quot;best of both worlds&amp;amp;quot; approach. Security Fix(es):</p> <p>The openssl crate before 0.10.55 for Rust allows an out-of-bounds read via an empty string to X509VerifyParamRef::set_host.(CVE-2023-53159)</p> <p>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.(CVE-2024-12224)</p> <p>A flaw was found in OpenSSL&amp;apos;s handling of the properties argument in certain functions. This vulnerability can allow use-after-free exploitation, which may result in undefined behavior or incorrect property parsing, leading to OpenSSL treating the input as an empty string.(CVE-2025-3416)</p> <p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: rpm-ostree</p> <p>rpm-ostree is a hybrid image/package system. It supports &amp;amp;quot;composing&amp;amp;quot; packages on a build server into an OSTree repository, which can then be replicated by client systems with atomic upgrades. Additionally, unlike many &amp;amp;quot;pure&amp;amp;quot; image systems, with rpm-ostree each client system can layer on additional packages, providing a &amp;amp;quot;best of both worlds&amp;amp;quot; approach. Security Fix(es):</p> <p>The openssl crate before 0.10.55 for Rust allows an out-of-bounds read via an empty string to X509VerifyParamRef::set_host.(CVE-2023-53159)</p> <p>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.(CVE-2024-12224)</p> <p>A flaw was found in OpenSSL&amp;apos;s handling of the properties argument in certain functions. This vulnerability can allow use-after-free exploitation, which may result in undefined behavior or incorrect property parsing, leading to OpenSSL treating the input as an empty string.(CVE-2025-3416)</p> https://cve.radiocsirt.org/vuln/oesa-2026-2944 https://cve.radiocsirt.org/vuln/opensuse-su-2025:15201-1 <p>python311-nh3-0.2.17-2.1 on GA media</p> <p>python311-nh3-0.2.17-2.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15201-1 https://cve.radiocsirt.org/vuln/rhsa-2025:17340 <p>idna: idna accepts Punycode labels that do not produce any non-ASCII when decoded firefox: thunderbird: Sandbox escape due to use-after-free in the Graphics: Canvas2D component firefox: thunderbird: Sandbox escape due to undefined behavior, invalid pointer in the Graphics: Canvas2D component firefox: thunderbird: Same-origin policy bypass in the Layout component firefox: thunderbird: Incorrect boundary conditions in the JavaScript: GC component firefox: thunderbird: Integer overflow in the SVG component firefox: thunderbird: Information disclosure in the Networking: Cache component firefox: thunderbird: Memory safety bugs fixed in Firefox ESR 140.3, Thunderbird ESR 140.3, Firefox 143 and Thunderbird 143</p> <p>idna: idna accepts Punycode labels that do not produce any non-ASCII when decoded firefox: thunderbird: Sandbox escape due to use-after-free in the Graphics: Canvas2D component firefox: thunderbird: Sandbox escape due to undefined behavior, invalid pointer in the Graphics: Canvas2D component firefox: thunderbird: Same-origin policy bypass in the Layout component firefox: thunderbird: Incorrect boundary conditions in the JavaScript: GC component firefox: thunderbird: Integer overflow in the SVG component firefox: thunderbird: Information disclosure in the Networking: Cache component firefox: thunderbird: Memory safety bugs fixed in Firefox ESR 140.3, Thunderbird ESR 140.3, Firefox 143 and Thunderbird 143</p> https://cve.radiocsirt.org/vuln/rhsa-2025:17340 https://cve.radiocsirt.org/vuln/rustsec-2024-0421 <p><strong>Affected:</strong> crates.io: idna</p> <p>`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.</p> <p>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.</p> <p>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.</p> <p>## Remedy</p> <p>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.)</p> <p>When upgrading, please take a moment to read about [alternative Unicode back ends for `idna`](https://docs.rs/crate/idna_adapter/latest).</p> <p>If you are using Rust earlier than 1.81 in combination with SQLx…</p> <p><strong>Affected:</strong> crates.io: idna</p> <p>`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.</p> <p>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.</p> <p>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.</p> <p>## Remedy</p> <p>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.)</p> <p>When upgrading, please take a moment to read about [alternative Unicode back ends for `idna`](https://docs.rs/crate/idna_adapter/latest).</p> <p>If you are using Rust earlier than 1.81 in combination with SQLx…</p> https://cve.radiocsirt.org/vuln/rustsec-2024-0421 https://cve.radiocsirt.org/vuln/suse-su-2025:02809-1 <p>Security update for rust-keylime</p> <p>Security update for rust-keylime</p> https://cve.radiocsirt.org/vuln/suse-su-2025:02809-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-12224 <p><strong>Affected:</strong> Ubuntu:20.04:LTS: rust-idna, Ubuntu:22.04:LTS: rust-idna, Ubuntu:24.04:LTS: rust-idna, Ubuntu:25.10: rust-idna, Ubuntu:26.04:LTS: rust-idna</p> <p>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.</p> <p><strong>Affected:</strong> Ubuntu:20.04:LTS: rust-idna, Ubuntu:22.04:LTS: rust-idna, Ubuntu:24.04:LTS: rust-idna, Ubuntu:25.10: rust-idna, Ubuntu:26.04:LTS: rust-idna</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-12224 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0686 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um einen Denial of Service Angriff durchzuführen, oder seine Privilegien zu erweitern.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um einen Denial of Service Angriff durchzuführen, oder seine Privilegien zu erweitern.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0686