GHSA-mjv9-vp6w-3rc9
MEDIUMAWS SDK for Rust will log AWS credentials when TRACE-level logging is enabled for request sending
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
aws-sigv4🦀aws-sigv4🦀aws-sigv4🦀aws-sigv4🦀aws-sigv4🦀aws-sigv4🦀aws-sigv4🦀aws-sigv4+15 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | aws-sigv4 | ≥ 0.55.0&&< 0.55.1 | 0.55.1 |
| 🦀crates.io | aws-sigv4 | ≥ 0.54.1&&< 0.54.2 | 0.54.2 |
| 🦀crates.io | aws-sigv4 | ≥ 0.53.1&&< 0.53.2 | 0.53.2 |
| 🦀crates.io | aws-sigv4 | ≥ 0.52.0&&< 0.52.1 | 0.52.1 |
| 🦀crates.io | aws-sigv4 | ≥ 0.51.0&&< 0.51.1 | 0.51.1 |
| 🦀crates.io | aws-sigv4 | ≥ 0.49.0&&< 0.49.1 | 0.49.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aws-sigv4. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update aws-sigv4 to 0.55.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mjv9-vp6w-3rc9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-mjv9-vp6w-3rc9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-mjv9-vp6w-3rc9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mjv9-vp6w-3rc9 in your dependencies?
O3 detects GHSA-mjv9-vp6w-3rc9 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.