Credential disclosure via derived SigningParams debug output
Published Apr 19, 2023 · Updated Feb 5, 2025
Information disclosure in the aws-sigv4 component of AWS SDK for Rust allows local users to read AWS credentials from TRACE logs. SigningParams derives Debug and emits the access key, secret key, and security token in plaintext when request-signing parameters are formatted. Exposure requires TRACE-level logging for the SDK globally or for aws-sigv4 and access to the resulting logs, enabling credential theft but not direct data modification or service interruption.
Summary
What happened
Information disclosure in the aws-sigv4 component of AWS SDK for Rust allows local users to read AWS credentials from TRACE logs. SigningParams derives Debug and emits the access key, secret key, and security token in plaintext when request-signing parameters are formatted. Exposure requires TRACE-level logging for the SDK globally or for aws-sigv4 and access to the resulting logs, enabling credential theft but not direct data modification or service interruption.
The record
- CVE
- CVE-2023-30610
- Published
- Apr 19, 2023
- Updated
- Feb 5, 2025
- Vendor
- Amazon Web Services
- Product
- AWS SDK for Rust
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 19, 2023CVE publishedPublication date reported by the CVE source.
- Feb 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.10.1, < 0.10.2
- Affected versionversion=>= 0.11.0, < 0.11.1
- Affected versionversion=>= 0.12.0, < 0.12.1
- Affected versionversion=>= 0.13.0, < 0.13.1
- Affected versionversion=>= 0.14.0, < 0.14.1
- Affected versionversion=>= 0.15.0, < 0.15.1
- Affected versionversion=>= 0.2.0, < 0.2.1
- Affected versionversion=>= 0.3.0, < 0.3.1
- Affected versionversion=>= 0.4.1, < 0.4.2
- Affected versionversion=>= 0.46.0, < 0.46.1
- Affected versionversion=>= 0.47.0, < 0.47.1
- Affected versionversion=>= 0.48.0, < 0.48.1
- Affected versionversion=>= 0.49.0, < 0.49.1
- Affected versionversion=>= 0.50.0, < 0.51.1
- Affected versionversion=>= 0.52.0, < 0.52.1,
- Affected versionversion=>= 0.5.2, < 0.5.3
- Affected versionversion=>= 0.53.1, < 0.53.2
- Affected versionversion=>= 0.54.1, < 0.54.2
- Affected versionversion=>= 0.55.0, < 0.55.1
- Affected versionversion=>= 0.6.0, < 0.6.1
- Affected versionversion=>= 0.7.0, < 0.7.1
- Affected versionversion=>= 0.8.0, < 0.8.1
- Affected versionversion=>= 0.9.0, < 0.9.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo