What is CVE-2023-30610?

CVE-2023-30610 is a medium-severity security vulnerability in aws-sigv4 (rust), affecting versions = 0.55.0. It is fixed in 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.

How severe is CVE-2023-30610?

CVE-2023-30610 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of aws-sigv4 are affected by CVE-2023-30610?

aws-sigv4 (rust) versions = 0.55.0 is affected.

Is CVE-2023-30610 exploitable, and should I be worried?

Whether CVE-2023-30610 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-30610 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2023-30610?

Upgrade: aws-sigv4 to 0.55.1 or later, aws-sigv4 to 0.54.2 or later, aws-sigv4 to 0.53.2 or later, aws-sigv4 to 0.52.1 or later, aws-sigv4 to 0.51.1 or later, aws-sigv4 to 0.49.1 or later, aws-sigv4 to 0.48.1 or later, aws-sigv4 to 0.47.1 or later, aws-sigv4 to 0.46.1 or later, aws-sigv4 to 0.15.1 or later, aws-sigv4 to 0.14.1 or later, aws-sigv4 to 0.13.1 or later, aws-sigv4 to 0.12.1 or later, aws-sigv4 to 0.11.1 or later, aws-sigv4 to 0.10.2 or later, aws-sigv4 to 0.9.1 or later, aws-sigv4 to 0.8.1 or later, aws-sigv4 to 0.7.1 or later, aws-sigv4 to 0.6.1 or later, aws-sigv4 to 0.5.3 or later, aws-sigv4 to 0.4.2 or later, aws-sigv4 to 0.3.1 or later, aws-sigv4 to 0.2.1 or later.

CVE-2023-30610 in aws-sigv4

Summary

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

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.

Workarounds

Disable TRACE-level logging for AWS Rust SDK crates.

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.

CVE-2023-30610 has a CVSS score of 5.5 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (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); upgrading removes the vulnerable code path.

Affected versions

aws-sigv4 (= 0.55.0) aws-sigv4 (= 0.54.1) aws-sigv4 (= 0.53.1) aws-sigv4 (= 0.52.0) aws-sigv4 (= 0.51.0) aws-sigv4 (= 0.49.0) aws-sigv4 (= 0.48.0) aws-sigv4 (= 0.47.0) aws-sigv4 (= 0.46.0) aws-sigv4 (= 0.15.0) aws-sigv4 (= 0.14.0) aws-sigv4 (= 0.13.0) aws-sigv4 (= 0.12.0) aws-sigv4 (= 0.11.0) aws-sigv4 (= 0.10.1) aws-sigv4 (= 0.9.0) aws-sigv4 (= 0.8.0) aws-sigv4 (= 0.7.0) aws-sigv4 (= 0.6.0) aws-sigv4 (= 0.5.2) aws-sigv4 (= 0.4.1) aws-sigv4 (= 0.3.0) aws-sigv4 (= 0.2.0)

Security releases

aws-sigv4 → 0.55.1 (rust) aws-sigv4 → 0.54.2 (rust) aws-sigv4 → 0.53.2 (rust) aws-sigv4 → 0.52.1 (rust) aws-sigv4 → 0.51.1 (rust) aws-sigv4 → 0.49.1 (rust) aws-sigv4 → 0.48.1 (rust) aws-sigv4 → 0.47.1 (rust) aws-sigv4 → 0.46.1 (rust) aws-sigv4 → 0.15.1 (rust) aws-sigv4 → 0.14.1 (rust) aws-sigv4 → 0.13.1 (rust) aws-sigv4 → 0.12.1 (rust) aws-sigv4 → 0.11.1 (rust) aws-sigv4 → 0.10.2 (rust) aws-sigv4 → 0.9.1 (rust) aws-sigv4 → 0.8.1 (rust) aws-sigv4 → 0.7.1 (rust) aws-sigv4 → 0.6.1 (rust) aws-sigv4 → 0.5.3 (rust) aws-sigv4 → 0.4.2 (rust) aws-sigv4 → 0.3.1 (rust) aws-sigv4 → 0.2.1 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is CVE-2023-30610? CVE-2023-30610 is a medium-severity security vulnerability in aws-sigv4 (rust), affecting versions = 0.55.0. It is fixed in 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.
How severe is CVE-2023-30610? CVE-2023-30610 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of aws-sigv4 are affected by CVE-2023-30610? aws-sigv4 (rust) versions = 0.55.0 is affected.
Is there a fix for CVE-2023-30610? Yes. CVE-2023-30610 is fixed in 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. Upgrade to this version or later.
Is CVE-2023-30610 exploitable, and should I be worried? Whether CVE-2023-30610 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-30610 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-30610?
- Upgrade aws-sigv4 to 0.55.1 or later
- Upgrade aws-sigv4 to 0.54.2 or later
- Upgrade aws-sigv4 to 0.53.2 or later
- Upgrade aws-sigv4 to 0.52.1 or later
- Upgrade aws-sigv4 to 0.51.1 or later
- Upgrade aws-sigv4 to 0.49.1 or later
- Upgrade aws-sigv4 to 0.48.1 or later
- Upgrade aws-sigv4 to 0.47.1 or later
- Upgrade aws-sigv4 to 0.46.1 or later
- Upgrade aws-sigv4 to 0.15.1 or later
- Upgrade aws-sigv4 to 0.14.1 or later
- Upgrade aws-sigv4 to 0.13.1 or later
- Upgrade aws-sigv4 to 0.12.1 or later
- Upgrade aws-sigv4 to 0.11.1 or later
- Upgrade aws-sigv4 to 0.10.2 or later
- Upgrade aws-sigv4 to 0.9.1 or later
- Upgrade aws-sigv4 to 0.8.1 or later
- Upgrade aws-sigv4 to 0.7.1 or later
- Upgrade aws-sigv4 to 0.6.1 or later
- Upgrade aws-sigv4 to 0.5.3 or later
- Upgrade aws-sigv4 to 0.4.2 or later
- Upgrade aws-sigv4 to 0.3.1 or later
- Upgrade aws-sigv4 to 0.2.1 or later