AWS SDK for Rust will log AWS credentials when TRACE-level logging is enabled for request sending
CVE-2023-30610GHSA-mjv9-vp6w-3rc9
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (aws-sigv4 0.55.1, 0.54.2, 0.53.2, 0.52.1, 0.51.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.4.2, 0.3.1, 0.2.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
crates.io aws-sigv4
- Affected
- >= 0.55.0, <= 0.55.0>= 0.54.1, <= 0.54.1>= 0.53.1, <= 0.53.1>= 0.52.0, <= 0.52.0>= 0.51.0, <= 0.51.0>= 0.49.0, <= 0.49.0>= 0.48.0, <= 0.48.0>= 0.47.0, <= 0.47.0>= 0.46.0, <= 0.46.0>= 0.15.0, <= 0.15.0>= 0.14.0, <= 0.14.0>= 0.13.0, <= 0.13.0>= 0.12.0, <= 0.12.0>= 0.11.0, <= 0.11.0>= 0.10.1, <= 0.10.1>= 0.9.0, <= 0.9.0>= 0.8.0, <= 0.8.0>= 0.7.0, <= 0.7.0>= 0.6.0, <= 0.6.0>= 0.5.2, <= 0.5.2>= 0.4.1, <= 0.4.1>= 0.3.0, <= 0.3.0>= 0.2.0, <= 0.2.0
- Fixed in
- 0.54.2, 0.15.1, 0.11.1, 0.47.1, 0.13.1, 0.52.1, 0.55.1, 0.5.3, 0.46.1, 0.48.1, 0.8.1, 0.3.1, 0.12.1, 0.9.1, 0.6.1, 0.51.1, 0.53.2, 0.10.2, 0.4.2, 0.14.1, 0.49.1, 0.2.1, 0.7.1
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-mjv9-vp6w-3rc9 lists affected ranges: crates.io aws-sigv4 >=0.55.0 =0.54.1 =0.53.1 =0.52.0 =0.51.0 =0.49.0 =0.48.0 =0.47.0 =0.46.0 =0.15.0 =0.14.0 =0.13.0 =0.12.0 =0.11.0 =0.10.1 =0.9.0 =0.8.0 =0.7.0 =0.6.0 =0.5.2 =0.4.1 =0.3.0 <=0.3.0,…
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.5 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- EPSS
- CVE-2023-30610: 0.21% estimated exploitation activity in the next 30 days; percentile 11.84 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
The awssigv4::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. RUSTLOG=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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-mjv9-vp6w-3rc9
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2023-30610 Advisory: AWS SDK for Rust will log AWS credentials when TRACE-level logging is enabled for request sending IDs: CVE-2023-30610, GHSA-mjv9-vp6w-3rc9 Record: https://patchnext.com/advisories/cve-2023-30610 (revision 1, source checked 26 Oct 2026, 15:42 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: aws-sigv4 0.55.1, 0.54.2, 0.53.2, 0.52.1, 0.51.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.4.2, 0.3.1, 0.2.1. A vendor fix does not mean a deployment is fixed. ## Affected components - crates.io aws-sigv4: affected >= 0.55.0, <= 0.55.0; >= 0.54.1, <= 0.54.1; >= 0.53.1, <= 0.53.1; >= 0.52.0, <= 0.52.0; >= 0.51.0, <= 0.51.0; >= 0.49.0, <= 0.49.0; >= 0.48.0, <= 0.48.0; >= 0.47.0, <= 0.47.0; >= 0.46.0, <= 0.46.0; >= 0.15.0, <= 0.15.0; >= 0.14.0, <= 0.14.0; >= 0.13.0, <= 0.13.0; >= 0.12.0, <= 0.12.0; >= 0.11.0, <= 0.11.0; >= 0.10.1, <= 0.10.1; >= 0.9.0, <= 0.9.0; >= 0.8.0, <= 0.8.0; >= 0.7.0, <= 0.7.0; >= 0.6.0, <= 0.6.0; >= 0.5.2, <= 0.5.2; >= 0.4.1, <= 0.4.1; >= 0.3.0, <= 0.3.0; >= 0.2.0, <= 0.2.0; fixed in 0.54.2, 0.15.1, 0.11.1, 0.47.1, 0.13.1, 0.52.1, 0.55.1, 0.5.3, 0.46.1, 0.48.1, 0.8.1, 0.3.1, 0.12.1, 0.9.1, 0.6.1, 0.51.1, 0.53.2, 0.10.2, 0.4.2, 0.14.1, 0.49.1, 0.2.1, 0.7.1 ## Suggested inspection (read-only) - crates.io aws-sigv4: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on aws-sigv4. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-mjv9-vp6w-3rc9 (GitHub-reviewed advisory GHSA-mjv9-vp6w-3rc9 lists affected ranges: crates.io aws-sigv4 >=0.55.0 =0.54.1 =0.53.1 =0.52.0 =0.51.0 =0.49.0 =0.48.0 =0.47.0 =0.46.0 =0.15.0 =0.14.0 =0.13.0 =0.12.0 =0.11.0 =0.10.1 =0.9.0 =0.8.0 =0.7.0 =0.6.0 =0.5.2 =0.4.1 =0.3.0 <=0.3.0,…) Commands are suggestions: review each one before running it.
Loading voting…