Skip to content
Noroxi
OSV ecosystem advisory

GHSA-464c-974j-9xm6: AWS CDK CodeBuild S3 Log Encryption Boolean Inversion

LowCVSS 3.3 · v3.1—No exploit Fix available

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
—

Report tools

JSON

Action score

13

Monitor

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.

Follow GHSA-464c-974j-9xm6

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
npmaws-cdk-lib
npm@aws-cdk/aws-codebuild
NuGetAmazon.CDK.Lib
Mavensoftware.amazon.awscdk:aws-cdk-lib
Gogithub.com/aws/aws-cdk-go/awscdk/v2
NuGetAmazon.CDK.AWS.CodeBuild
Mavensoftware.amazon.awscdk:codebuild
Gogithub.com/aws/aws-cdk-go/awscdk
PyPIaws-cdk-aws-codebuild

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/aws/aws-cdk-go/awscdkfrom 1.175.0-devpreview—
Gogithub.com/aws/aws-cdk-go/awscdkfrom 1.175.0-devpreview · up to and including 1.204.0-devpreview—
Gogithub.com/aws/aws-cdk-go/awscdk/v2before 2.253.02.253.0
Mavensoftware.amazon.awscdk:aws-cdk-libbefore 2.253.02.253.0
Mavensoftware.amazon.awscdk:codebuildfrom 1.75.0 · up to and including 1.204.0—
npm@aws-cdk/aws-codebuildfrom 1.75.0 · up to and including 1.204.0—
npmaws-cdk-libbefore 2.253.02.253.0
NuGetAmazon.CDK.AWS.CodeBuildfrom 1.75.0 · up to and including 1.204.0—
NuGetAmazon.CDK.Libbefore 2.253.02.253.0
PyPIaws-cdk-aws-codebuildfrom 1.75.0 · up to and including 1.204.0—
PyPIaws-cdk-libbefore 2.253.02.253.0

Same product

npm: all records

Other 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 Construct
    26Monitor
  • GHSA-5pq3-h73f-66hrAWS CDK CodePipeline: trusted entities are too broad
    15Monitor
  • GHSA-qc59-cxj2-c2w4aws-cdk-lib's aspect order change causes different Permissions Boundary assigned to Role
    8Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/aws/aws-cdk-go/awscdk/v22.253.0Package registry (OSV)
Maven:software.amazon.awscdk:aws-cdk-lib2.253.0Package registry (OSV)
npm:aws-cdk-lib2.253.0Package registry (OSV)
NuGet:Amazon.CDK.Lib2.253.0Package registry (OSV)
PyPI:aws-cdk-lib2.253.0Package 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

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

osv

References

All records