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.
This vulnerability carries a MEDIUM severity rating with a CVSS v3.1 score of 5.5, requiring local system access to exploit with relatively low complexity without requiring user interaction requiring only low-level privileges . The vulnerability impacts confidentiality (data exposure), for affected systems. Impacting 1 product from amazon organizations running these solutions should prioritize assessment and patching.
Reported in 2023, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2023-04-19T18:15:07.417
2025-02-05T15:15:19.460
Modified
CVSSv3.1: 5.5 (MEDIUM)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | amazon | aws-sigv4 | 0.2.0 | Yes |
| Application | amazon | aws-sigv4 | 0.3.0 | Yes |
| Application | amazon | aws-sigv4 | 0.4.1 | Yes |
| Application | amazon | aws-sigv4 | 0.5.2 | Yes |
| Application | amazon | aws-sigv4 | 0.6.0 | Yes |
| Application | amazon | aws-sigv4 | 0.7.0 | Yes |
| Application | amazon | aws-sigv4 | 0.8.0 | Yes |
| Application | amazon | aws-sigv4 | 0.9.0 | Yes |
| Application | amazon | aws-sigv4 | 0.10.1 | Yes |
| Application | amazon | aws-sigv4 | 0.11.0 | Yes |
| Application | amazon | aws-sigv4 | 0.12.0 | Yes |
| Application | amazon | aws-sigv4 | 0.13.0 | Yes |
| Application | amazon | aws-sigv4 | 0.14.0 | Yes |
| Application | amazon | aws-sigv4 | 0.15.0 | Yes |
| Application | amazon | aws-sigv4 | 0.46.0 | Yes |
| Application | amazon | aws-sigv4 | 0.47.0 | Yes |
| Application | amazon | aws-sigv4 | 0.48.0 | Yes |
| Application | amazon | aws-sigv4 | 0.49.0 | Yes |
| Application | amazon | aws-sigv4 | 0.50.0 | Yes |
| Application | amazon | aws-sigv4 | 0.51.0 | Yes |
| Application | amazon | aws-sigv4 | 0.52.0 | Yes |
| Application | amazon | aws-sigv4 | 0.53.1 | Yes |
| Application | amazon | aws-sigv4 | 0.54.1 | Yes |
| Application | amazon | aws-sigv4 | 0.55.0 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For amazon's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.