Aws Sdk Rust
Approved changes feed: RSS · Atom
cpe:2.3:a:awslabs:aws-sdk-rust:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Awslabs (400e7466-79c7-523c-b85f-b53f8baa53ad) |
|---|---|
| Product | Aws Sdk Rust (bd664f9b-6332-5293-b688-68bac91dbed3) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-30610 |
vulnerable | 2026-06-08 06:04:39.932579 |
AWS SDK for Rust will log AWS credentials when TRACE-level logging is enabled for request sending
MEDIUM (5.5)
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.
Published: 2023-04-19T17:18:54.703Z
Updated: 2025-02-05T14:56:14.270Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.