Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go☕ Maven📦 npm.NET NuGet🐍 PyPI

GHSA-464c-974j-9xm6

LOW

AWS CDK CodeBuild S3 Log Encryption Boolean Inversion

Published
Jul 24, 2026
Updated
Jul 24, 2026
Affected
10 pkgs
Patched
5 / 10
Exploits
None indexed

Blast Radius

10 pkgs affected
🐹github.com/aws/aws-cdk-go/awscdk/v2🐹github.com/aws/aws-cdk-go/awscdk☕software.amazon.awscdk:aws-cdk-lib☕software.amazon.awscdk:codebuild📦aws-cdk-lib📦@aws-cdk/aws-codebuild.NETAmazon.CDK.Lib.NETAmazon.CDK.AWS.CodeBuild+2 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go, Maven packages — download data is not available via public APIs for these ecosystems.

Description

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 [email protected]. 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.

Affected Packages

10 total 5 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/aws/aws-cdk-go/awscdk/v2all versions2.253.0
🐹Gogithub.com/aws/aws-cdk-go/awscdk≥ 1.175.0-devpreviewNo fix
☕Mavensoftware.amazon.awscdk:aws-cdk-liball versions2.253.0
☕Mavensoftware.amazon.awscdk:codebuild≥ 1.75.0No fix
📦npmaws-cdk-liball versions2.253.0
📦npm@aws-cdk/aws-codebuild≥ 1.75.0No fix

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/aws/aws-cdk-go/awscdk/v2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/aws/aws-cdk-go/awscdk/v2 to 2.253.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-464c-974j-9xm6 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-464c-974j-9xm6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-464c-974j-9xm6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## 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 t
O3 Security · Impact-Aware SCA

Is GHSA-464c-974j-9xm6 in your dependencies?

O3 detects GHSA-464c-974j-9xm6 across Go, Maven, npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works