dbcve.org
Aws Sigv4Application · Amazon

CVE-2023-30610

MEDIUM · 5.5 CVSS v3.1 Published 2023-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The aws-sigv4 Rust library's `SigningParams` struct included a derived Debug implementation that exposed AWS credentials (access key, secret key, security token) in plaintext. When TRACE-level logging was enabled for the AWS SDK for Rust, these credentials were written to logs, allowing unauthorized access to sensitive authentication material.

MitigationUpgrade to the patched version of aws-sigv4 via Cargo dependency update, or disable TRACE-level logging for AWS Rust SDK crates if unable to upgrade.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Aws Sigv4Application
Affected:= 0.2.0= 0.3.0= 0.4.1= 0.5.2= 0.6.0= 0.7.0= 0.8.0= 0.9.0= 0.10.1= 0.11.0= 0.12.0= 0.13.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify aws-sigv4 dependency version
    Inspect your project Cargo.lock file and search for the aws-sigv4 crate entry to find the installed version number
    Affected if The version listed matches any of: 0.2.0, 0.3.0, 0.4.1, 0.5.2, 0.6.0, 0.7.0, 0.8.0, 0.9.0, 0.10.1, 0.11.0, 0.12.0, 0.13.0
  2. Confirm TRACE logging is enabled for AWS SDK
    Check your logging configuration (RUST_LOG environment variable, log4rs.yaml, or code-based logger setup) for a TRACE-level setting targeting aws-sdk, aws-http, or sigv4 crates
    Affected if TRACE level logging is enabled for any AWS Rust SDK crate
  3. Search application logs for plaintext credentials
    Search your application log files or log aggregation system for patterns matching AWS access key IDs (typically starting with AKIA) or secret access keys in plaintext
    Affected if Log output contains AWS access key or secret key in human-readable text

You are affected if your project uses an affected aws-sigv4 version AND TRACE-level logging was enabled, resulting in credentials present in logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to the patched version of aws-sigv4 via Cargo dependency update, or disable TRACE-level logging for AWS Rust SDK crates if unable to upgrade.

Recommended fix Moderate confidence

latest available version (newer than 0.5.2)

  1. Check your current aws-sigv4 version in Cargo.toml
  2. Update aws-sigv4 to the latest available version using: cargo update aws-sigv4
  3. Alternatively, upgrade the aws-sdk-rust crate which will pull in the fixed aws-sigv4 version
  4. Verify the update was successful by running: cargo tree | grep aws-sigv4
  5. Ensure no sensitive credentials are being logged by checking your logging configuration
  6. If you cannot upgrade, add a filter to disable TRACE-level logging for aws-sigv4 crates (e.g., RUST_LOG=warn or set specific filters excluding aws_sigv4)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aws Sigv4 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30610 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-30610 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data