Medium, CVSS 5.5crates.ioPublished
AWS SDK for Rust will log AWS credentials when TRACE-level logging is enabled for request sending
CVE-2023-30610 · GHSA-mjv9-vp6w-3rc9
- Affected
- crates.io aws-sigv4 >= 0.55.0, <= 0.55.0; >= 0.54.1, <= 0.54.1; >= 0.53.1, <= 0.53.1; >= 0.52.0, <= 0.52.0; >= 0.51.0, <= 0.51.0; >= 0.49.0, <= 0.49.0; >= 0.48.0, <= 0.48.0; >= 0.47.0, <= 0.47.0; >= 0.46.0, <= 0.46.0; >= 0.15.0, <= 0.15.0; >= 0.14.0, <= 0.14.0; >= 0.13.0, <= 0.13.0; >= 0.12.0, <= 0.12.0; >= 0.11.0, <= 0.11.0; >= 0.10.1, <= 0.10.1; >= 0.9.0, <= 0.9.0; >= 0.8.0, <= 0.8.0; >= 0.7.0, <= 0.7.0; >= 0.6.0, <= 0.6.0; >= 0.5.2, <= 0.5.2; >= 0.4.1, <= 0.4.1; >= 0.3.0, <= 0.3.0; >= 0.2.0, <= 0.2.0
- Fixed in
- 0.54.20.15.10.11.10.47.10.13.10.52.10.55.10.5.30.46.10.48.10.8.10.3.10.12.10.9.10.6.10.51.10.53.20.10.20.4.20.14.10.49.10.2.10.7.1· Vendor fix available
- Issue
- The awssigv4::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. RUSTLOG=trace), or for the aws-sigv4 crate specifically. Patches - Versions = 0.55.1 - 0.54.2 - 0.53.2 - 0.52.1 - 0.51.1 - 0.50.1 - 0.49.1 - 0.48.1 - 0.47.1 - 0.46.1 - 0.15.1 - 0.14.1 - 0.13.1 - 0.12.1 - 0.11.1 - 0.10.2 - 0.9.1 - 0.8.1 - 0.7.1 - 0.6.1 - 0.5.3 - 0.3.1 - 0.2.1 Workarounds Disable TRACE-level logging for AWS Rust SDK crates.
Recommended action: Upgrade to 0.55.1, 0.54.2, 0.53.2 or 20 more by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.