Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.21% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2023
CVE-2023-30610High confidence
AWS SDK for Rust will log AWS credentials when TRACE-level logging is enabled for request sending
awslabs · aws-sdk-rust
Official source article: GitHub GHSA-MJV9-VP6W-3RC9 ↗. Check the applicable product and release in the original source.
5.5MediumCVSS 3.1
Scheduled
Fix not verifiedMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Low, lowered one band.downgradedsince 5 Feb 2025
Compensating controls
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs awslabs aws-sdk-rust and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Open-source package ranges23 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| rustaws-sigv4 | = 0.55.0 | 0.55.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.54.1 | 0.54.2 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.53.1 | 0.53.2 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.52.0 | 0.52.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.51.0 | 0.51.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.49.0 | 0.49.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.48.0 | 0.48.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.47.0 | 0.47.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.46.0 | 0.46.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.15.0 | 0.15.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.14.0 | 0.14.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.13.0 | 0.13.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.12.0 | 0.12.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.11.0 | 0.11.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.10.1 | 0.10.2 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.9.0 | 0.9.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.8.0 | 0.8.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.7.0 | 0.7.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.6.0 | 0.6.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.5.2 | 0.5.3 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.4.1 | 0.4.2 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.3.0 | 0.3.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
| rustaws-sigv4 | = 0.2.0 | 0.2.1 | GitHub advisory ↗upstream repository advisory · 6 Apr 2026 |
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Fix not verified01
What, why and how
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.
What
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.
Why
The product writes sensitive information to a log file.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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.
Why
The product writes sensitive information to a log file.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Insertion of Sensitive Information into Log File → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-532 ↗
CWE-532: Insertion of Sensitive Information into Log File. The product writes sensitive information to a log file.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix not verified
- Affected
- 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, >= 0.14.0, < 0.14.1, >= 0.15.0, < 0.15.1, >= 0.46.0, < 0.46.1, >= 0.47.0, < 0.47.1, >= 0.48.0, < 0.48.1, >= 0.49.0, < 0.49.1, >= 0.50.0, < 0.51.1, >= 0.52.0, < 0.52.1, , >= 0.53.1, < 0.53.2, >= 0.54.1, < 0.54.2, >= 0.55.0, < 0.55.1
- Fixed
- No fixed version is explicitly recorded in the structured CVE data.
- Action
- No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 19 Apr 2023 · Last source change 5 Feb 2025, 14:56 UTC · CWE-532 · Insertion of Sensitive Information into Log File
CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2023-1355
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.