Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: aws-sigv4 (crates.io) 0.2.1, 0.10.2, 0.11.1.

Low priority for now. Upgrade to aws-sigv4 (crates.io) 0.2.1, 0.10.2, 0.11.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Apr 19, 2023
Updated
Jun 17, 2026
EPSS
0.2% · 11th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · GitHub_M
5.5
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-30610

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for amazon records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
amazonaws-sigv4

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • amazon aws-sigv40.10.1
  • amazon aws-sigv40.11.0
  • amazon aws-sigv40.12.0
  • amazon aws-sigv40.13.0
  • amazon aws-sigv40.14.0
  • amazon aws-sigv40.15.0
  • amazon aws-sigv40.2.0
  • amazon aws-sigv40.3.0
  • amazon aws-sigv40.4.1
  • amazon aws-sigv40.46.0
  • amazon aws-sigv40.47.0
  • amazon aws-sigv40.48.0
  • amazon aws-sigv40.49.0
  • amazon aws-sigv40.5.2
  • amazon aws-sigv40.50.0
  • amazon aws-sigv40.51.0
  • amazon aws-sigv40.52.0
  • amazon aws-sigv40.53.1
  • amazon aws-sigv40.54.1
  • amazon aws-sigv40.55.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • awslabs aws-sdk-rust

    • >= 0.2.0, < 0.2.1, >= 0.3.0, < 0.3.1, >= 0.4.1, < 0.4.2, >= 0.5.2, < 0.5.3, >= 0.6.0, < 0.6.1, >= 0.7.0, < 0.7.1, >= 0.8.0, < 0.8.1, >= 0.9.0, < 0.9.1, >= 0.10.1, < 0.10.2, >= 0.11.0, < 0.11.1, >= 0.12.0, < 0.12.1, >= 0.13.0, < 0.13.1 … (+11)affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
crates.ioaws-sigv4from 0.0.0-0 · before 0.2.10.2.1
crates.ioaws-sigv4from 0.10.0-0 · before 0.10.20.10.2
crates.ioaws-sigv4from 0.10.1 · before 0.10.20.10.2
crates.ioaws-sigv4from 0.11.0 · before 0.11.10.11.1
crates.ioaws-sigv4from 0.11.0-0 · before 0.11.10.11.1
crates.ioaws-sigv4from 0.12.0 · before 0.12.10.12.1
crates.ioaws-sigv4from 0.12.0-0 · before 0.12.10.12.1
crates.ioaws-sigv4from 0.13.0 · before 0.13.10.13.1
crates.ioaws-sigv4from 0.13.0-0 · before 0.13.10.13.1
crates.ioaws-sigv4from 0.14.0 · before 0.14.10.14.1
crates.ioaws-sigv4from 0.14.0-0 · before 0.14.10.14.1
crates.ioaws-sigv4from 0.15.0 · before 0.15.10.15.1
crates.ioaws-sigv4from 0.15.0-0 · before 0.15.10.15.1
crates.ioaws-sigv4from 0.16.0-0 · before 0.46.10.46.1
crates.ioaws-sigv4from 0.2.0 · before 0.2.10.2.1
crates.ioaws-sigv4from 0.3.0 · before 0.3.10.3.1
crates.ioaws-sigv4from 0.3.0-0 · before 0.3.10.3.1
crates.ioaws-sigv4from 0.4.0-0 · before 0.5.30.5.3
crates.ioaws-sigv4from 0.4.1 · before 0.4.20.4.2
crates.ioaws-sigv4from 0.46.0 · before 0.46.10.46.1
crates.ioaws-sigv4from 0.47.0 · before 0.47.10.47.1
crates.ioaws-sigv4from 0.47.0-0 · before 0.47.10.47.1
crates.ioaws-sigv4from 0.48.0 · before 0.48.10.48.1
crates.ioaws-sigv4from 0.48.0-0 · before 0.48.10.48.1

+22

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
crates.io:aws-sigv40.10.2Package registry (OSV)
crates.io:aws-sigv40.11.1Package registry (OSV)
crates.io:aws-sigv40.12.1Package registry (OSV)
crates.io:aws-sigv40.13.1Package registry (OSV)
crates.io:aws-sigv40.14.1Package registry (OSV)
crates.io:aws-sigv40.15.1Package registry (OSV)
crates.io:aws-sigv40.2.1Package registry (OSV)
crates.io:aws-sigv40.3.1Package registry (OSV)
crates.io:aws-sigv40.4.2Package registry (OSV)
crates.io:aws-sigv40.46.1Package registry (OSV)
crates.io:aws-sigv40.47.1Package registry (OSV)
crates.io:aws-sigv40.48.1Package registry (OSV)
crates.io:aws-sigv40.49.1Package registry (OSV)
crates.io:aws-sigv40.5.3Package registry (OSV)
crates.io:aws-sigv40.50.1Package registry (OSV)
crates.io:aws-sigv40.51.1Package registry (OSV)
crates.io:aws-sigv40.52.1Package registry (OSV)
crates.io:aws-sigv40.53.2Package registry (OSV)
crates.io:aws-sigv40.54.2Package registry (OSV)
crates.io:aws-sigv40.55.1Package registry (OSV)
crates.io:aws-sigv40.6.1Package registry (OSV)
crates.io:aws-sigv40.7.1Package registry (OSV)
crates.io:aws-sigv40.8.1Package registry (OSV)
crates.io:aws-sigv40.9.1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-532 · Insertion of Sensitive Information into Log File

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records