vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2023-30610

AWS SDK for Rust will log AWS credentials when TRACE-level logging is enabled for request sending

MEDIUM
5.5
CVSS Score
Published: April 19, 2023 at 05:18 PM UTC
Updated: June 17, 2026 at 05:55 AM UTC
2 products affected across 2 vendorsAWS SIGV4AWS SIGV4

Using aws-sdk-rust by awslabs?

Get instant alerts when new vulnerabilities affect aws-sdk-rust - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

AWS SIGV4· Amazoncargo
95%
0.10.10.11.00.12.00.13.00.14.00.15.00.2.00.3.00.4.10.46.00.47.00.48.00.49.00.5.20.50.00.51.00.52.00.53.10.54.10.55.00.6.00.7.00.8.00.9.0
AWS SIGV4· Awslabs
60%
v < 0.10.2v < 0.11.1v < 0.12.1v < 0.13.1v < 0.14.1v < 0.15.1v < 0.2.1v < 0.3.1v < 0.4.2v < 0.46.1v < 0.47.1v < 0.48.1v < 0.49.1v < 0.5.3v < 0.51.1v < 0.52.1v < 0.53.2v < 0.54.2v < 0.55.1v < 0.6.1v < 0.7.1v < 0.8.1v < 0.9.1
Affected range stops below 0.10.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.11.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.12.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.13.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.14.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.15.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.2.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.3.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.4.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.46.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.47.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.48.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.49.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.5.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.51.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.52.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.53.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.54.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.55.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.6.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.7.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.8.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 0.9.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

x_refsource_CONFIRMVendor Advisory
Source: [email protected]
https://github.com/awslabs/aws-sdk-rust/security/advisories/GHSA-mjv9-vp6w-3rc9

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMGitHub_M
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-532

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card