CVE-2025-23206
Amazon Aws Cloud Development Kit ≤ 2.177.0
Raw vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:A/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-23206 is a low-severity Improper Verification of Cryptographic Signature (CWE-347) vulnerability in Amazon Aws Cloud Development Kit. Its CVSS base score is 1.8 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Supply Chain Compromise (T1195); ranked at the 25th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SI-7 (Software, Firmware, and Information Integrity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-23206 is a vulnerability in the AWS Cloud Development Kit (AWS CDK), an open-source framework for defining and provisioning AWS infrastructure via CloudFormation. It specifically affects users of the IAM OIDC custom resource provider package, where the `tls.connect` method always sets `rejectUnauthorized: false` during the workflow to download CA Thumbprints from a user-provided OIDC issuer URL. This disables TLS certificate validation, contrary to best practices that recommend `rejectUnauthorized: true`.
The vulnerability has a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), associated with CWE-347. Exploitation requires low privileges (PR:L) and can occur over the network with low complexity and no user interaction. An attacker could potentially perform a man-in-the-middle attack to intercept or tamper with CA Thumbprints, leading to high confidentiality and integrity impacts. However, the advisory designates it low severity due to user control over the issuer URL and execution within a Lambda environment, which mitigates practical MITM risks.
Mitigation requires upgrading to AWS CDK v2.177.0, expected on 2025-02-22. Post-upgrade, users must enable the feature flag '@aws-cdk/aws-iam:oidcRejectUnauthorizedConnections' set to true in `cdk.context.json` or `cdk.json`, as the change is opt-in to avoid breaking existing applications. No workarounds are available. Details are in AWS CDK GitHub issues #32920 and #32921, pull request #32921, the external.ts source code, and feature flag documentation.
This vulnerability has no reported real-world exploitation. The patch remains in progress as of the CVE publication on 2025-01-17.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-0113
Vulnerability Data
The AWS Cloud Development Kit (AWS CDK) is an open-source software development framework to define cloud infrastructure in code and provision it through AWS CloudFormation. Users who use IAM OIDC custom resource provider package will download CA Thumbprints as part…
more
of the custom resource workflow. However, the current `tls.connect` method will always set `rejectUnauthorized: false` which is a potential security concern. CDK should follow the best practice and set `rejectUnauthorized: true`. However, this could be a breaking change for existing CDK applications and we should fix this with a feature flag. Note that this is marked as low severity Security advisory because the issuer url is provided by CDK users who define the CDK application. If they insist on connecting to a unauthorized OIDC provider, CDK should not disallow this. Additionally, the code block is run in a Lambda environment which mitigate the MITM attack. The patch is in progress. To mitigate, upgrade to CDK v2.177.0 (Expected release date 2025-02-22). Once upgraded, users should make sure the feature flag '@aws-cdk/aws-iam:oidcRejectUnauthorizedConnections' is set to true in `cdk.context.json` or `cdk.json`. There are no known workarounds for this vulnerability.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 14 hardening rules · 5 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Requiring cryptographic protection mechanisms forces correct signature verification to be implemented for data protection.
Mandating integrity verification tools directly requires proper cryptographic signature checking to detect unauthorized changes.
Protecting session authenticity requires correct verification of cryptographic signatures or equivalent mechanisms.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Digital signatures are explicitly cited to protect integrity of data-at-rest, so proper verification directly mitigates the weakness.
Digital signatures are explicitly cited to protect integrity of data-in-transit, so proper verification directly mitigates the weakness.
Requires assessing authenticity and integrity of acquired assets, which commonly relies on signature verification but is limited to pre-acquisition.
Secure SDLC practices include code signing and signature verification requirements, addressing the weakness during development.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Establishing approved cryptographic solutions and usage practices lowers the probability that signature-verification steps will be omitted or incorrectly implemented.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (2 rules)
- V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-347
- V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-347
Oracle Linux 9 (2 rules)
- V-271525 OL 9 must have GPG signature verification enabled for all software repositories. prevents CWE-347
- V-271523 OL 9 must check the GPG signature of locally installed software packages before installation. prevents CWE-347
RHEL 7 (2 rules)
- V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-347
- V-204448 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-347
RHEL 8 (1 rule)
- V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-347
RHEL 9 (1 rule)
- V-257822 RHEL 9 must have GPG signature verification enabled for all software repositories. prevents CWE-347