CVE-2023-30610 AWS SDK for Rust will log AWS credentials when TRACE-level logging is enabled for request sending
Enabling TRACE-level logging in the AWS SDK for Rust exposes AWS credentials in logs, allowing attackers with log access to steal them.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-30610?
CVE-2023-30610 is a medium-severity vulnerability in awslabs aws-sdk-rust, published on 19 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
aws-sigv4 is a rust library for low level request signing in the aws cloud platform. 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. 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 are affected. This issue has been addressed in a set of new releases. Users are advised to upgrade. Users unable to upgrade should disable TRACE-level logging for AWS Rust SDK crates.
Weakness: CWE-532
Which versions are affected by CVE-2023-30610?
40 open source packages ship an affected version, including aws-sigv4. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
aws-sigv4 crates.io | From 0.0.0-0 | 0.2.1, 0.3.1, 0.5.3, 0.6.1, 0.7.1, 0.8.1, 0.9.1, 0.10.2, 0.11.1, 0.12.1, 0.13.1, 0.14.1, 0.15.1, 0.46.1, 0.47.1, 0.48.1, 0.49.1, 0.50.1, 0.51.1, 0.52.1, 0.53.2, 0.54.2, 0.55.1 |
aws-sigv4 crates.io | From 0.10.1 | 0.10.2 |
aws-sigv4 crates.io | From 0.10.1 | 0.10.2 |
aws-sigv4 crates.io | From 0.11.0 | 0.11.1 |
aws-sigv4 crates.io | From 0.11.0 | 0.11.1 |
aws-sigv4 crates.io | From 0.12.0 | 0.12.1 |
34 more packages
aws-sigv4 crates.io | From 0.12.0 | 0.12.1 |
aws-sigv4 crates.io | From 0.13.0 | 0.13.1 |
aws-sigv4 crates.io | From 0.13.0 | 0.13.1 |
aws-sigv4 crates.io | From 0.14.0 | 0.14.1 |
aws-sigv4 crates.io | From 0.14.0 | 0.14.1 |
aws-sigv4 crates.io | From 0.15.0 | 0.15.1 |
aws-sigv4 crates.io | From 0.15.0 | 0.15.1 |
aws-sigv4 crates.io | From 0.2.0 | 0.2.1 |
aws-sigv4 crates.io | From 0.2.0 | 0.2.1 |
aws-sigv4 crates.io | From 0.3.0 | 0.3.1 |
aws-sigv4 crates.io | From 0.3.0 | 0.3.1 |
aws-sigv4 crates.io | From 0.4.1 | 0.4.2 |
aws-sigv4 crates.io | From 0.4.1 | 0.4.2 |
aws-sigv4 crates.io | From 0.46.0 | 0.46.1 |
aws-sigv4 crates.io | From 0.46.0 | 0.46.1 |
aws-sigv4 crates.io | From 0.47.0 | 0.47.1 |
aws-sigv4 crates.io | From 0.47.0 | 0.47.1 |
aws-sigv4 crates.io | From 0.48.0 | 0.48.1 |
aws-sigv4 crates.io | From 0.48.0 | 0.48.1 |
aws-sigv4 crates.io | From 0.49.0 | 0.49.1 |
aws-sigv4 crates.io | From 0.49.0 | 0.49.1 |
aws-sigv4 crates.io | From 0.5.2 | 0.5.3 |
aws-sigv4 crates.io | From 0.5.2 | 0.5.3 |
aws-sigv4 crates.io | From 0.51.0 | 0.51.1 |
aws-sigv4 crates.io | From 0.51.0 | 0.51.1 |
aws-sigv4 crates.io | From 0.52.0 | 0.52.1 |
aws-sigv4 crates.io | From 0.52.0 | 0.52.1 |
aws-sigv4 crates.io | From 0.53.1 | 0.53.2 |
aws-sigv4 crates.io | From 0.53.1 | 0.53.2 |
aws-sigv4 crates.io | From 0.54.1 | 0.54.2 |
aws-sigv4 crates.io | From 0.54.1 | 0.54.2 |
aws-sigv4 crates.io | From 0.55.0 | 0.55.1 |
aws-sigv4 crates.io | From 0.55.0 | 0.55.1 |
aws-sigv4 crates.io | From 0.6.0 | 0.6.1 |
Products include Amazon Aws-Sigv4.
How do I fix CVE-2023-30610?
Upgrade aws-sigv4 to a fixed version for your release line: 0.2.1, 0.3.1, 0.5.3 or 0.6.1.
Is CVE-2023-30610 being exploited?
There is no known exploitation of CVE-2023-30610 in the wild and no public exploit code.
Sources
Also known as GHSA-mjv9-vp6w-3rc9, RUSTSEC-2023-0125.