Advisory
GHSA-mjv9-vp6w-3rc9
Also known as: CVE-2023-30610, RUSTSEC-2023-0125
Summary
AWS SDK for Rust will log AWS credentials when TRACE-level logging is enabled for request sending
Details
The aws_sigv4::SigningParams struct had a derived Debug implementation. When debug-formatted, it would include a user's AWS access key, AWS secret key, and security token in plaintext. When TRACE-level logging is enabled for an SDK, SigningParams is printed, thereby revealing those credentials to anyone with access to logs.
Impact
All users of the AWS SDK for Rust who enabled TRACE-level logging, either globally (e.g. RUST_LOG=trace), or for the aws-sigv4 crate specifically.
Patches
- Versions >=
0.55.1 0.54.20.53.20.52.10.51.10.50.10.49.10.48.10.47.10.46.10.15.10.14.10.13.10.12.10.11.10.10.20.9.10.8.10.7.10.6.10.5.30.3.10.2.1
Workarounds
Disable TRACE-level logging for AWS Rust SDK crates.
Severity
Medium Basis: The source's own band: MODERATE
Dates
- Published
- 2023-04-26 16:01 UTC
- Modified
- 2026-04-06 17:38 UTC
Affected packages and fixes
| Package | Affected | Fix |
|---|---|---|
| aws-sigv4 | introduced 0.55.0, fixed 0.55.1 | cargo update -p aws-sigv4 --precise 0.55.1 |
| aws-sigv4 | introduced 0.54.1, fixed 0.54.2 | cargo update -p aws-sigv4 --precise 0.54.2 |
| aws-sigv4 | introduced 0.53.1, fixed 0.53.2 | cargo update -p aws-sigv4 --precise 0.53.2 |
| aws-sigv4 | introduced 0.52.0, fixed 0.52.1 | cargo update -p aws-sigv4 --precise 0.52.1 |
| aws-sigv4 | introduced 0.51.0, fixed 0.51.1 | cargo update -p aws-sigv4 --precise 0.51.1 |
| aws-sigv4 | introduced 0.49.0, fixed 0.49.1 | cargo update -p aws-sigv4 --precise 0.49.1 |
| aws-sigv4 | introduced 0.48.0, fixed 0.48.1 | cargo update -p aws-sigv4 --precise 0.48.1 |
| aws-sigv4 | introduced 0.47.0, fixed 0.47.1 | cargo update -p aws-sigv4 --precise 0.47.1 |
| aws-sigv4 | introduced 0.46.0, fixed 0.46.1 | cargo update -p aws-sigv4 --precise 0.46.1 |
| aws-sigv4 | introduced 0.15.0, fixed 0.15.1 | cargo update -p aws-sigv4 --precise 0.15.1 |
| aws-sigv4 | introduced 0.14.0, fixed 0.14.1 | cargo update -p aws-sigv4 --precise 0.14.1 |
| aws-sigv4 | introduced 0.13.0, fixed 0.13.1 | cargo update -p aws-sigv4 --precise 0.13.1 |
| aws-sigv4 | introduced 0.12.0, fixed 0.12.1 | cargo update -p aws-sigv4 --precise 0.12.1 |
| aws-sigv4 | introduced 0.11.0, fixed 0.11.1 | cargo update -p aws-sigv4 --precise 0.11.1 |
| aws-sigv4 | introduced 0.10.1, fixed 0.10.2 | cargo update -p aws-sigv4 --precise 0.10.2 |
| aws-sigv4 | introduced 0.9.0, fixed 0.9.1 | cargo update -p aws-sigv4 --precise 0.9.1 |
| aws-sigv4 | introduced 0.8.0, fixed 0.8.1 | cargo update -p aws-sigv4 --precise 0.8.1 |
| aws-sigv4 | introduced 0.7.0, fixed 0.7.1 | cargo update -p aws-sigv4 --precise 0.7.1 |
| aws-sigv4 | introduced 0.6.0, fixed 0.6.1 | cargo update -p aws-sigv4 --precise 0.6.1 |
| aws-sigv4 | introduced 0.5.2, fixed 0.5.3 | cargo update -p aws-sigv4 --precise 0.5.3 |
| aws-sigv4 | introduced 0.4.1, fixed 0.4.2 | cargo update -p aws-sigv4 --precise 0.4.2 |
| aws-sigv4 | introduced 0.3.0, fixed 0.3.1 | cargo update -p aws-sigv4 --precise 0.3.1 |
| aws-sigv4 | introduced 0.2.0, fixed 0.2.1 | cargo update -p aws-sigv4 --precise 0.2.1 |
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Links
Source
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0