NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🦀
🦀 crates.io
Not in CISA KEV
MEDIUM severity

AWS SDK for Rust will log AWS credentials when TRACE-level logging is enabled for request sendingGHSA-mjv9-vp6w-3rc9

MEDIUM

GHSA-mjv9-vp6w-3rc9 is a medium-severity (CVSS 5.5) CWE-532 vulnerability in aws-sigv4. A fix is available for aws-sigv4 — see the affected versions and patch details below.

Also known asCVE-2023-30610RUSTSEC-2023-0125
Published
Updated
Affected
23 pkgs
Patched
23 / 23
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-mjv9-vp6w-3rc9.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk
0.00%0.24%0.48%0.72%0.1%0.2%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

23 pkgs affected
🦀aws-sigv4🦀aws-sigv4🦀aws-sigv4🦀aws-sigv4🦀aws-sigv4🦀aws-sigv4🦀aws-sigv4🦀aws-sigv4+15 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

Impact

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.

Patches

  • Versions >= 0.55.1
  • 0.54.2
  • 0.53.2
  • 0.52.1
  • 0.51.1
  • 0.50.1
  • 0.49.1
  • 0.48.1
  • 0.47.1
  • 0.46.1
  • 0.15.1
  • 0.14.1
  • 0.13.1
  • 0.12.1
  • 0.11.1
  • 0.10.2
  • 0.9.1
  • 0.8.1
  • 0.7.1
  • 0.6.1
  • 0.5.3
  • 0.3.1
  • 0.2.1

Workarounds

Disable TRACE-level logging for AWS Rust SDK crates.

Affected Packages

23 total 23 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.ioaws-sigv4≥ 0.55.0&&< 0.55.10.55.1cargo update -p aws-sigv4 --precise 0.55.1
🦀crates.ioaws-sigv4≥ 0.54.1&&< 0.54.20.54.2cargo update -p aws-sigv4 --precise 0.54.2
🦀crates.ioaws-sigv4≥ 0.53.1&&< 0.53.20.53.2cargo update -p aws-sigv4 --precise 0.53.2
🦀crates.ioaws-sigv4≥ 0.52.0&&< 0.52.10.52.1cargo update -p aws-sigv4 --precise 0.52.1
🦀crates.ioaws-sigv4≥ 0.51.0&&< 0.51.10.51.1cargo update -p aws-sigv4 --precise 0.51.1
🦀crates.ioaws-sigv4≥ 0.49.0&&< 0.49.10.49.1cargo update -p aws-sigv4 --precise 0.49.1

Affected Products

1 product · 24 configurations
Application
aws-sigv4amazon
24 versions
0.2.00.3.00.4.10.5.20.6.00.7.00.8.00.9.00.10.10.11.00.12.00.13.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aws-sigv4, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update aws-sigv4 to 0.55.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mjv9-vp6w-3rc9 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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. ### Impact 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. ### Patches - Versions >= `0.55.1` - `0.54.2` - `0.53.2` - `0.52.1` - `0.51.1` - `0.50.1` - `0.49.1` - `
O3 Security · Impact-Aware SCA

Is GHSA-mjv9-vp6w-3rc9 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works
AWS SDK for Rust will log AWS credentials when…