GHSA-464c-974j-9xm6: AWS CDK CodeBuild S3 Log Encryption Boolean Inversion
Noroxi assessment
Priority: Monitor (action score 13/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: github.com/aws/aws-cdk-go/awscdk/v2 (Go) 2.253.0; software.amazon.awscdk:aws-cdk-lib (Maven) 2.253.0; aws-cdk-lib (npm) 2.253.0.
Low priority for now. Upgrade to github.com/aws/aws-cdk-go/awscdk/v2 (Go) 2.253.0; software.amazon.awscdk:aws-cdk-lib (Maven) 2.253.0; aws-cdk-lib (npm) 2.253.0 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: OSV
## Summary The AWS Cloud Development Kit (AWS CDK) is an open-source software development framework for defining cloud infrastructure in code and provisioning it through AWS CloudFormation. We identified an issue in which explicitly setting `encrypted: true` on the `S3LoggingOptions` property of an AWS CodeBuild project construct produces the opposite of the intended behavior, disabling encryption on CodeBuild build logs stored in S3. ## Impact The `S3LoggingOptions.encrypted` property in the `aws-codebuild` module uses positive polarity (`true` = encryption ON), but is mapped directly to the CloudFormation `S3LogsConfig.EncryptionDisabled` field, which uses negative polarity (`true` = encryption OFF). Because the value is not negated before being passed to CloudFormation, any explicit assignment produces inverted behavior: * Setting `encrypted: true` (intending encryption ON) causes CloudFormation to receive `EncryptionDisabled: true`, disabling encryption. * Setting `encrypted: false` (intending encryption OFF) causes CloudFormation to receive `EncryptionDisabled: false`, enabling encryption. Users who omit the property entirely are not affected, as `undefined` passes through to CloudFormation, which defaults to encryption enabled. Users affected by this issue could have CodeBuild S3 build logs stored using SSE-S3 (Amazon S3-managed keys, AES-256) rather than the AWS managed keys that CodeBuild applies by default. Since January 5, 2023, Amazon S3 automatically encrypts all new object uploads with SSE-S3, so logs written after that date remain encrypted at rest. However, logs written prior to that date to buckets that did not have default encryption configured at the time are potentially not encrypted at rest. Impacted versions: >= 1.75.0 and <= 2.252.0 ## Patches This issue has been addressed in `aws-cdk-lib` version 2.253.0. Upgrade to the latest version and ensure any forked or derivative code is patched to incorporate the new fixes. ## Workarounds Users who are unable to immediately upgrade to version 2.253.0 should omit the `encrypted` property from their `S3LoggingOptions` configuration entirely. When the property is omitted, the value is not passed to CloudFormation, and CodeBuild applies its default behavior of encrypting build logs using AWS managed keys. ## References If you have any questions or comments about this advisory, contact AWS Security via our issue reporting page \[1\] or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue. \[1\] <https://aws.amazon.com/security/vulnerability-reporting/> ## Acknowledgement AWS thanks AISafe for collaborating on this issue through the coordinated disclosure process.
- Published
- Jul 24, 2026
- Updated
- Sep 10, 2026
- EPSS
- —
- CWE
- CWE-311
Report tools
Action score
13
Low priority for now.
- CVSS
- 13 / 40 · 3.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| npm | aws-cdk-lib | pkg:npm/aws-cdk-lib |
| npm | @aws-cdk/aws-codebuild | pkg:npm/%40aws-cdk/aws-codebuild |
| NuGet | Amazon.CDK.Lib | pkg:nuget/Amazon.CDK.Lib |
| Maven | software.amazon.awscdk:aws-cdk-lib | pkg:maven/software.amazon.awscdk/aws-cdk-lib |
| Go | github.com/aws/aws-cdk-go/awscdk/v2 | pkg:golang/github.com/aws/aws-cdk-go/awscdk/v2 |
| NuGet | Amazon.CDK.AWS.CodeBuild | pkg:nuget/Amazon.CDK.AWS.CodeBuild |
| Maven | software.amazon.awscdk:codebuild | pkg:maven/software.amazon.awscdk/codebuild |
| Go | github.com/aws/aws-cdk-go/awscdk | pkg:golang/github.com/aws/aws-cdk-go/awscdk |
| PyPI | aws-cdk-aws-codebuild | pkg:pypi/aws-cdk-aws-codebuild |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/aws/aws-cdk-go/awscdk | from 1.175.0-devpreview | — |
| Go | github.com/aws/aws-cdk-go/awscdk | from 1.175.0-devpreview · up to and including 1.204.0-devpreview | — |
| Go | github.com/aws/aws-cdk-go/awscdk/v2 | before 2.253.0 | 2.253.0 |
| Maven | software.amazon.awscdk:aws-cdk-lib | before 2.253.0 | 2.253.0 |
| Maven | software.amazon.awscdk:codebuild | from 1.75.0 · up to and including 1.204.0 | — |
| npm | @aws-cdk/aws-codebuild | from 1.75.0 · up to and including 1.204.0 | — |
| npm | aws-cdk-lib | before 2.253.0 | 2.253.0 |
| NuGet | Amazon.CDK.AWS.CodeBuild | from 1.75.0 · up to and including 1.204.0 | — |
| NuGet | Amazon.CDK.Lib | before 2.253.0 | 2.253.0 |
| PyPI | aws-cdk-aws-codebuild | from 1.75.0 · up to and including 1.204.0 | — |
| PyPI | aws-cdk-lib | before 2.253.0 | 2.253.0 |
Same product
npm: all recordsOther highest-scoring records for the same primary product.
- GHSA-qq4x-c6h6-rfxhaws-cdk-lib has Insertion of Sensitive Information into Log File vulnerability when using Cognito UserPoolClient Construct26Monitor
- GHSA-5pq3-h73f-66hrAWS CDK CodePipeline: trusted entities are too broad15Monitor
- GHSA-qc59-cxj2-c2w4aws-cdk-lib's aspect order change causes different Permissions Boundary assigned to Role8Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/aws/aws-cdk-go/awscdk/v2 | 2.253.0 | Package registry (OSV) |
| Maven:software.amazon.awscdk:aws-cdk-lib | 2.253.0 | Package registry (OSV) |
| npm:aws-cdk-lib | 2.253.0 | Package registry (OSV) |
| NuGet:Amazon.CDK.Lib | 2.253.0 | Package registry (OSV) |
| PyPI:aws-cdk-lib | 2.253.0 | Package 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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-311 · Missing Encryption of Sensitive DataCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Sniffing AttacksCAPEC-157Medium
- Sniffing Network TrafficCAPEC-158Medium
- Lifting Sensitive Data Embedded in CacheCAPEC-204Medium
- Accessing/Intercepting/Modifying HTTP CookiesCAPEC-31likelihood: High · High
- Retrieve Embedded Sensitive DataCAPEC-37likelihood: High · Very High
- Harvesting Information via API Event MonitoringCAPEC-383Low
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.