# CVE-2023-30610: AWS SDK for Rust will log AWS credentials when TRACE-level logging is enabled for request sending > Enabling TRACE-level logging in the AWS SDK for Rust exposes AWS credentials in logs, allowing attackers with log access to steal them. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Apr 2023 - **Updated:** 5 Feb 2025 - **Also known as:** GHSA-mjv9-vp6w-3rc9, RUSTSEC-2023-0125 ## What is CVE-2023-30610? CVE-2023-30610 is a medium-severity vulnerability in awslabs aws-sdk-rust, published on 19 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description 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. Weakness: CWE-532 (Insertion of Sensitive Information into Log File) ## Which versions are affected by CVE-2023-30610? 40 open source packages ship an affected version, including aws-sigv4. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `aws-sigv4` | crates.io | From 0.0.0-0 | 0.2.1, 0.3.1, 0.5.3, 0.6.1, 0.7.1, 0.8.1, 0.9.1, 0.10.2, 0.11.1, 0.12.1, 0.13.1, 0.14.1, 0.15.1, 0.46.1, 0.47.1, 0.48.1, 0.49.1, 0.50.1, 0.51.1, 0.52.1, 0.53.2, 0.54.2, 0.55.1 | | `aws-sigv4` | crates.io | From 0.10.1 | 0.10.2 | | `aws-sigv4` | crates.io | From 0.10.1 | 0.10.2 | | `aws-sigv4` | crates.io | From 0.11.0 | 0.11.1 | | `aws-sigv4` | crates.io | From 0.11.0 | 0.11.1 | | `aws-sigv4` | crates.io | From 0.12.0 | 0.12.1 | | `aws-sigv4` | crates.io | From 0.12.0 | 0.12.1 | | `aws-sigv4` | crates.io | From 0.13.0 | 0.13.1 | | `aws-sigv4` | crates.io | From 0.13.0 | 0.13.1 | | `aws-sigv4` | crates.io | From 0.14.0 | 0.14.1 | | `aws-sigv4` | crates.io | From 0.14.0 | 0.14.1 | | `aws-sigv4` | crates.io | From 0.15.0 | 0.15.1 | | `aws-sigv4` | crates.io | From 0.15.0 | 0.15.1 | | `aws-sigv4` | crates.io | From 0.2.0 | 0.2.1 | | `aws-sigv4` | crates.io | From 0.2.0 | 0.2.1 | | `aws-sigv4` | crates.io | From 0.3.0 | 0.3.1 | | `aws-sigv4` | crates.io | From 0.3.0 | 0.3.1 | | `aws-sigv4` | crates.io | From 0.4.1 | 0.4.2 | | `aws-sigv4` | crates.io | From 0.4.1 | 0.4.2 | | `aws-sigv4` | crates.io | From 0.46.0 | 0.46.1 | | `aws-sigv4` | crates.io | From 0.46.0 | 0.46.1 | | `aws-sigv4` | crates.io | From 0.47.0 | 0.47.1 | | `aws-sigv4` | crates.io | From 0.47.0 | 0.47.1 | | `aws-sigv4` | crates.io | From 0.48.0 | 0.48.1 | | `aws-sigv4` | crates.io | From 0.48.0 | 0.48.1 | | `aws-sigv4` | crates.io | From 0.49.0 | 0.49.1 | | `aws-sigv4` | crates.io | From 0.49.0 | 0.49.1 | | `aws-sigv4` | crates.io | From 0.5.2 | 0.5.3 | | `aws-sigv4` | crates.io | From 0.5.2 | 0.5.3 | | `aws-sigv4` | crates.io | From 0.51.0 | 0.51.1 | | `aws-sigv4` | crates.io | From 0.51.0 | 0.51.1 | | `aws-sigv4` | crates.io | From 0.52.0 | 0.52.1 | | `aws-sigv4` | crates.io | From 0.52.0 | 0.52.1 | | `aws-sigv4` | crates.io | From 0.53.1 | 0.53.2 | | `aws-sigv4` | crates.io | From 0.53.1 | 0.53.2 | | `aws-sigv4` | crates.io | From 0.54.1 | 0.54.2 | | `aws-sigv4` | crates.io | From 0.54.1 | 0.54.2 | | `aws-sigv4` | crates.io | From 0.55.0 | 0.55.1 | | `aws-sigv4` | crates.io | From 0.55.0 | 0.55.1 | | `aws-sigv4` | crates.io | From 0.6.0 | 0.6.1 | Products: Amazon Aws-Sigv4. ## How do I fix CVE-2023-30610? Upgrade aws-sigv4 to a fixed version for your release line: 0.2.1, 0.3.1, 0.5.3 or 0.6.1. ## Is CVE-2023-30610 being exploited? There is no known exploitation of CVE-2023-30610 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-30610 and fix it if it is affected. What it is: CVE-2023-30610 is a medium-severity vulnerability in awslabs aws-sdk-rust, published on 19 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-30610 in the wild and no public exploit code. Affected packages and fixed versions: - aws-sigv4 (crates.io): affected from 0.0.0-0; fixed in 0.2.1, 0.3.1, 0.5.3, 0.6.1, 0.7.1, 0.8.1, 0.9.1, 0.10.2, 0.11.1, 0.12.1, 0.13.1, 0.14.1, 0.15.1, 0.46.1, 0.47.1, 0.48.1, 0.49.1, 0.50.1, 0.51.1, 0.52.1, 0.53.2, 0.54.2, 0.55.1 - aws-sigv4 (crates.io): affected from 0.10.1; fixed in 0.10.2 - aws-sigv4 (crates.io): affected from 0.10.1; fixed in 0.10.2 - aws-sigv4 (crates.io): affected from 0.11.0; fixed in 0.11.1 - aws-sigv4 (crates.io): affected from 0.11.0; fixed in 0.11.1 - aws-sigv4 (crates.io): affected from 0.12.0; fixed in 0.12.1 - aws-sigv4 (crates.io): affected from 0.12.0; fixed in 0.12.1 - aws-sigv4 (crates.io): affected from 0.13.0; fixed in 0.13.1 - aws-sigv4 (crates.io): affected from 0.13.0; fixed in 0.13.1 - aws-sigv4 (crates.io): affected from 0.14.0; fixed in 0.14.1 - aws-sigv4 (crates.io): affected from 0.14.0; fixed in 0.14.1 - aws-sigv4 (crates.io): affected from 0.15.0; fixed in 0.15.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-30610/ (Markdown: https://insights.sbomify.com/CVE-2023-30610/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-30610 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-30610 - OSV: https://osv.dev/vulnerability/CVE-2023-30610 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-30610/ Summaries are generated and may contain mistakes; the official description above is the record.