CVE-2024-12224VulnerabilityPublished 2 Oct 2026Updated 10 Nov 2026

SUSE · Security update for rustup

Affects SUSESource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2024-12224· Medium 5.1

Not known to be exploited · CVSS 5.1 Medium · fixed in SUSE package updates : update SUSE idna when convenient.

Data as of 10 Nov 2026, 20:06 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 1.29.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

Attack Vector: Network
Attack Complexity: High
Attack Requirements: Present
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: High
Subsequent system integrity: Low
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: High: There is a total loss of confidentiality, resulting in all resources within the Subsequent System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
crates.ioidna`pkg:cargo/idna`Other threats	Affected =0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

This update for rustup fixes the following issues: - CVE-2024-12224: idna: idna accepts Punycode labels that do not produce any non-ASCII when decoded (bsc#1243862). - CVE-2025-58160: tracing-subscriber: Tracing log pollution (bsc#1249008). - CVE-2026-25541: bytes: integer overflow in 'BytesMut:reserve' can lead to undefined behavior and crashes (bsc#1274144). - CVE-2026-25727: time: parsing of user-provided input by the RFC 2822 date parser can lead to stack exhaustion (bsc#1257902). - CVE-2026-41676: openssl: `Deriver:derive` and `PkeyCtxRef:derive` can overflow short buffers on OpenSSL 1.1.1 (bsc#1270186). - CVE-2026-41677: openssl: out-of-bounds read in PEM password callback when returning an oversized length in rust- openssl crate (bsc#1270619). - CVE-2026-41678: openssl: incorrect bounds assertion in aes key wrap in rust-openssl crate (bsc#1270644). - CVE-2026-41681: openssl: MdCtxRef::digest_final() writes past caller buffer with no length check in rust-openssl crate (bsc#1270795). - CVE-2026-41898: openssl: unchecked callback-returned length in PSK and cookie generate trampolines can leak adjacent memory in rust-openssl crate (bsc#1270870). - CVE-2026-42327: openssl: arbitrary code execution via specially crafted certificate in rust-openssl crate (bsc#1270521). - CVE-2026-44662: openssl: heap buffer overflow when encrypting with AES key-wrap-with-padding in rust-openssl crate (bsc#1270874). - CVE-2026-45784: openssl: out-of-bounds write in `CipherCtxRef::cipher_update_inplace` for AES-KW-PAD ciphers in rust- openssl crate (bsc#1270989). - CVE-2026-93599: rustls-webpki: panic via empty BIT STRING (bsc#1282217). - CVE-2026-93600: rustls-webpki: name constraints URI validation bypass (bsc#1282217). - CVE-2026-93601: rustls-webpki: name constraint bypass (bsc#1282217). - CVE-2026-93602: rustls-webpki: CRL revocation check bypass (bsc#1282217). - rust-shlex: Multiple issues involving quote API (RUSTSEC-2024-0006, GHSA-r7qv-8r2h-pg27) (bsc#1230032). Changes for rustup: - Update to version 1.29.1~0: * dist(rustup-init/sh): update commit shasum in help string * style(bin/rustup-init): reformat code * docs(changelog): update for v1.29.1 stable release * warn how to switch away from the deprecated complete profile * fix(cli/help): fix wording in `rustup run --help` * ci(docker/android): stop building OpenSSL * refactor(cli/docs): use tracing for docs opening status messages * refactor(self-update): rename Windows uninstall registry helpers * feat(test): isolate Windows registry state per test * docs(dev-guide): mention how to support new compilation targets * Fix funding link * chore(deps): lock file maintenance * refactor(cli/self-update): move `current_install_opts()` to `InstallOpts::display()` * refactor(cli/self-update): move `process` out of `InstallOpts` * fix(cli/self-update): postpone initialization of `Cfg` in `setup_mode` * refactor(cli/self-update): take `Process` in `check_existence_of_settings_file()` * fix(settings): prevent creating new file with `SettingsFile::read_settings()` * test(cli-inst-interactive): test file creation on cancelled installation * refactor(toolchain/names): inline `validate()` aliases into `FromStr` * refactor(toolchain/names): rename `validate()` to `normalize_name()` * fix minor typos * www: align copy icon * refactor(toolchain/names)!: remove `try_from_str!()` * refactor(toolchain/names)!: remove `from_variant!()` * Add `rustup doc --serve` to serve docs over local HTTP * Move doc() and man() into a new docs module * chore(github): comment out instructions in PR template * docs(dev-guide): reapply abandoned changes from #4970 * Add riscv64 unknown linux musl support * fix(deps): update rust crate enum-map to v3 * refactor(cli/self-update)!: rename `install()` to `InstallOpts::install()` * refactor(cli/self-update)!: rename `maybe_install_rust()` to `InstallOpts::install_rust()` * refactor(cli/self-update)!: rename `InstallOpts::install()` to `InstallOpts::select_toolchain()` * refactor(toolchain/names)!: make more clones during conversions explicit * refactor(cli/self-update): move message templates to `mod msg` * style(cli/self-update): reorganize imports * Add pull request template linking to the dev guide * doc: add AI policy to the dev guide * ci(dist): ensure pushing to `dev-static` on `stable` update * test(toolchain): add a test case for `rustup toolchain install --override` * feat(toolchain): add `--default` flag to `rustup toolchain install` * fix(toolchain): inline use of `set_override` * Add Enzyme to the list of rustup components * fix: repair toolchains without an installed manifest * refactor: expose the installed manifest path * Docs: Remove i686 `set default-host` example * fix(self-update): only remove complete profile lines * chore(deps): bump `platforms` to 4.1.0 * chore(deps): remove pinned `openssl-src` * refactor: replace `cfg_if!{}` with `cfg_select!{}` * fix: Lock state fil

GCVE source: db.gcve.eu
Csaf Category: csaf_security_advisory
Csaf Version: 2.0
Publisher: SUSE Product Security Team
Advisory ID: openSUSE-SU-2026:22016-1
Vendor Severity: high
CVE Count: 16
Additional Cves: 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

References

Community reviews

Loading reviews…