Build environment compiled into the library and readable at runtime
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 0.6.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The rustpython-vm Rust crate (earlier releases up to 0.5.0, fixed in 0.6.0) embeds all environment variables from its build into compiled binaries, so any secrets present during the build, such as registry tokens, cloud credentials, and API keys, can be read from those binaries. Software that depends on this crate and was built with secrets in its environment, including published release binaries, may expose that sensitive data to anyone who has the binary.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
The build script of `rustpython-vm` 0.3.0 through 0.5.0 writes every environment variable of the build into `$OUT_DIR/env_vars.rs`. The crate compiles that file into `_sysconfigdata`'s `build_time_vars`. That module is always compiled. A binary built in CI with secrets in the environment carries those secrets in clear text. Registry tokens, cloud credentials and API keys are the usual ones. Anyone with the binary can read them with `strings` or from Python. Version 0.6.0 removes the dump and the include. Users of earlier versions should upgrade, rebuild, and ship new binaries. Every secret that was in the environment of a past build whose output left the build machine should be treated as exposed. Jacob Finkelman first reported the issue in #8802. Bitbison's automated supply chain scanning then detected credential data from the build environment flowing into artifacts that third-party software ships in the wild. The leak was confirmed in the published release binaries of at least four dependants but others have been impacted.
Timeline
- Advisory published
- Record last updated
Affected versions
- rustpython-vmcrates.io
From 0.3.0 · fixed in 0.6.0