fix: update dependency aws-cdk-lib to v2.246.0 [security]#563
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.179.0→2.246.0aws-cdk-lib has Insertion of Sensitive Information into Log File vulnerability when using Cognito UserPoolClient Construct
GHSA-qq4x-c6h6-rfxh
More information
Details
Summary
The AWS Cloud Development Kit (CDK) is an open-source framework for defining cloud infrastructure using code. Customers use it to create their own applications which are converted to AWS CloudFormation templates during deployment to a customer’s AWS account. CDK contains pre-built components called "constructs" that are higher-level abstractions providing defaults and best practices. This approach enables developers to use familiar programming languages to define complex cloud infrastructure more efficiently than writing raw CloudFormation templates.
The CDK Cognito UserPool construct deploys an AWS cognito user pool. An Amazon Cognito user pool is a user directory for web and mobile app authentication and authorization. Customers can deploy a client under this user pool through construct ‘UserPoolClient’ or through helper method 'addClient'. A user pool client resource represents an Amazon Cognito user pool client which is a configuration within a user pool that interacts with one mobile or web application authenticating with Amazon Cognito.
When users of the 'cognito.UserPoolClient' construct generate a secret value for the application client in AWS CDK, they can then reference the generated secrets in their stack. The CDK had an issue where, when the custom resource performed an SDK API call to 'DescribeCognitoUserPoolClient' to retrieve the generated secret, the full response was logged in the associated lambda function's log group. Any user authenticated in the account where logs of the custom resource are accessible and who has read-only permission could view the secret written to those logs.
This issue does not affect customers who are generating the secret value outside of the CDK as the secret is not referenced or logged.
Impact
To leverage this issue, an actor has to be authenticated in the account where logs of the custom resource Custom::DescribeCognitoUserPoolClient are accessible and have read-only permission for lambda function logs.
Users can review access to their log group through AWS CloudTrail logs to detect any unexpected access to read the logs.
Impacted versions: >2.37.0 and <=2.187.0
Patches
The patches are included in the AWS CDK Library release v2.187.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. To fully address this issue, users should rotate the secret by generating a new secret stored in AWS Secrets Manager. References to the secret will use the new secret on update.
When new CDK applications using the latest version are initialized, they will use the new behavior with updated logging.
Existing applications must upgrade to the latest version, change the feature flag (@aws-cdk/cognito:logUserPoolClientSecretValue) to false, redeploy the application to apply this fix and use the new implementation with updated logging behavior.
Workarounds
Users can override the implementation changing Logging to be Logging.withDataHidden(). For example define class CustomUserPoolClient extends UserPoolClient and in the new class define get userPoolClientSecret() to use Logging.withDataHidden().
Example
References
If you have any questions or comments about this advisory please contact AWS/Amazon Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
Severity
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
aws-cdk-lib's aspect order change causes different Permissions Boundary assigned to Role
GHSA-qc59-cxj2-c2w4
More information
Details
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. In the CDK, developers organize their applications into reusable components called "constructs," which are organized into a hierarchical tree structure. One of the features of this framework is the ability to call "Aspects," which are mechanisms to set configuration options for all AWS Resources in a particular part of the hierarchy at once. Aspect execution happens in a specific order, and the last Aspect to execute controls the final values in the template.
AWS CDK version 2.172.0 introduced a new priority system for Aspects. Prior to this version, CDK would run Aspects based on hierarchical location. The new priority system takes precedence over hierarchical location, altering the invocation order of Aspects. Different priority classes were introduced: Aspects added by CDK APIs were classified as MUTATING (priority 200), while Aspects added directly by the user were classified as DEFAULT (priority 500) unless the user specified otherwise. As a result of this change, CDK apps that use a custom Aspect to assign a default permissions boundary and then use a built-in CDK method to override it on select resources could have unexpected permissions boundaries assigned.
The following is an affected code sample:
In versions prior to 2.172.0, the Aspect added by {2} would invoke last and assign its permissions boundary to the Lambda function role.
In versions 2.172.0 and after, the Aspect added by {2} would have priority 200 while the Aspect added by {1} would have priority 500 and therefore be invoked last. The Lambda function role would get the permissions boundary of {1} assigned, which may not be what users expect.
Impact
If an unexpected permissions boundary is selected for a role, it could lead to that role having insufficient permissions. Alternatively, this could lead to a role having wider permissions than intended; however, this could happen only in combination with an overly permissive role policy, as permissions boundaries do not grant permissions by themselves.
Impacted versions: versions 2.172.0 up until 2.189.1
Patches
In version 2.189.1, the behavior has been reverted to the behavior of pre-2.172.0. The new behavior is available through a feature flag:
{ "context": { "@​aws-cdk/core:aspectPrioritiesMutating": true } }The patches are included in AWS CDK Library version 2.189.1 and after. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
Workarounds
As a workaround, users can use the location hierarchy to order the invocation of Aspects. To do this, users can assign the custom Aspect a priority of MUTATING to ensure it has the same priority as the Aspect added by the CDK API, and that the location hierarchy is used for the order of invocation Aspects.
The following code is an example:
References
If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
Credit
We would like to thank GoDaddy for collaborating on this issue through the coordinated vulnerability disclosure process.
Severity
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
AWS CDK CodePipeline: trusted entities are too broad
GHSA-5pq3-h73f-66hr
More information
Details
Summary
The AWS Cloud Development Kit (CDK) is an open-source framework for defining cloud infrastructure using code. Users use it to create their own applications, which are converted to AWS CloudFormation templates during deployment to a user's AWS account. AWS CDK contains pre-built components called "constructs," which are higher-level abstractions providing defaults and best practices. This approach enables developers to use familiar programming languages to define complex cloud infrastructure more efficiently than writing raw CloudFormation templates.
The AWS CodePipeline construct deploys CodePipeline, a managed service that orchestrates software release processes through a series of stages, each comprising one or more actions executed by CodePipeline. To perform these actions, CodePipeline assumes IAM roles with permissions necessary for each step, allowing it to interact with AWS services and resources on behalf of the user.
An issue exists where, when using CDK to create a CodePipeline with the CDK Construct Library, CDK creates an AWS Identity and Access Management (AWS IAM) trust policy with overly broad permissions. Any user with unrestricted sts:AssumeRole permissions could assume that trust policy. This issue does not affect users who supply their own role for CodePipeline.
Impact
To leverage the issue, an actor has to be authenticated in the account and have an unrestricted sts:AssumeRole permission. The permissions an actor could leverage depend on the actions added to the pipeline. Possible permissions include actions on services such as CloudFormation, CodeCommit, Lambda, and ECS, as well as access to the S3 bucket holding pipeline build artifacts (see documentation).
Users can review their AWS CloudTrail logs for when the role was assumed to determine if this was expected.
Impacted versions: <v2.189.0
Patches
The patches are included in the CDK Construct Library release v2.189.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
When new CDK applications using the latest version are initialized, they will use the new behavior with more restrictive permissions.
Existing applications must upgrade to the latest version, change the feature flag (@aws-cdk/pipelines:reduceStageRoleTrustScope) and (@aws-cdk/pipelines:reduceCrossAccountActionRoleTrustScope) to true and redeploy the application to apply this fix and use the new behavior with more restrictive permissions.
Workarounds
You can explicitly supply the role for your CodePipeline and follow the policy recommendations detailed in CodePipeline documentation.
References
Original reporting issue.
If you have any questions or comments about this advisory please contact AWS/Amazon Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
Severity
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
aws-cdk-lib: OS Command Injection in NodejsFunction Bundling
CVE-2026-11417 / GHSA-999r-qq7v-r334
More information
Details
Summary
AWS CDK (
aws-cdk-lib) is an open-source framework for defining cloud infrastructure in code and provisioning it through AWS CloudFormation. OS command injection in theNodejsFunctionlocal bundling pipeline inaws-cdk-libbefore 2.245.0 (2.246.0 on Windows) might allow a threat actor who controls the value of one or more bundling properties (externalModules,define,loader,inject, oresbuildArgs) to execute arbitrary commands on the host running the CDK toolchain via injected shell metacharacters. This issue requires the threat actor to control the value of one or more of the affected bundling properties in the CDK application.Impact
During local Lambda bundling,
NodejsFunctionassembled an esbuild command string from the bundling propertiesexternalModules,define,loader,inject, andesbuildArgsand executed it via a shell (bash -con Linux/macOS,cmd /con Windows) throughspawnSync. The property values were interpolated without escaping or validation, so values containing shell metacharacters could execute arbitrary commands with the privileges of the user runningcdk synth,cdk deploy, orcdk diff. Exploitation requires a threat actor to control one or more of the affected property values in the CDK application — for example via an untrusted npm dependency that vends a wrapper construct, or via a pull request that introduces untrusted values.Impacted versions:
< 2.245.0 (on Windows, < 2.246.0)
Patches
This issue has been addressed in
aws-cdk-libversion 2.245.0 (PR #37292), with a Windows-specific regression fix in 2.246.0 (PR #37412). The fix replaces shell-based command execution with array-basedspawnSyncinvocation that does not invoke a shell. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.Workarounds
Ensure the values supplied to
NodejsFunctionbundling properties (externalModules,define,loader,inject,esbuildArgs) originate only from trusted sources, and audit third-party constructs and pull requests that set them. Upgrading to a fixed version is the recommended remediation.References
If you have any questions or comments about this advisory, we ask that you contact AWS Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.
Acknowledgement
AWS would like to thank the external researcher Hesham Ashraf who reported this issue through the AWS Vulnerability Disclosure Program (HackerOne) for collaborating on it through the coordinated vulnerability disclosure process.
Severity
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
aws/aws-cdk (aws-cdk-lib)
v2.246.0Compare Source
Features
Bug Fixes
Reverts
Alpha modules (2.246.0-alpha.0)
v2.245.0Compare Source
Features
Bug Fixes
Alpha modules (2.245.0-alpha.0)
Features
v2.244.0Compare Source
Features
actions()method to Grants classes (#36987) (bbeaf5d)Bug Fixes
Alpha modules (2.244.0-alpha.0)
Bug Fixes
v2.243.0Compare Source
Features
Bug Fixes
Alpha modules (2.243.0-alpha.0)
v2.242.0Compare Source
⚠ BREAKING CHANGES
** L1 resources are automatically generated from public CloudFormation Resource Schemas. They are built to closely reflect the real state of CloudFormation. Sometimes these updates can contain changes that are incompatible with previous types, but more accurately reflect reality. In this release we have changed:
Features
PropertyMergeStrategyto merge arbitrary CFN property objects (#37206) (793ad97)s3andecsservice mixins are now available inaws-cdk-lib(#37151) (52c99da)Bug Fixes
Assetuses a lot of memory (#37186) (70cae75)enableAutoSoftwareUpdate: falseis not reflected in the CloudFormation template (#37152) (dec8e6f), closes #36382Alpha modules (2.242.0-alpha.0)
Features
v2.241.0Compare Source
⚠ BREAKING CHANGES
aws-codedeploy: AWS::CodeDeploy::DeploymentGroup: Id attribute removed.
Features
Bug Fixes
Alpha modules (2.241.0-alpha.0)
Features
recordFieldsandoutputFormatto Vended Logs Mixin (#37042) (dd94c31)v2.240.0Compare Source
Features
Bug Fixes
Alpha modules (2.240.0-alpha.0)
v2.239.0Compare Source
⚠ BREAKING CHANGES
aws-licensemanager: AWS::LicenseManager::License: Beneficiary property is now required
aws-licensemanager: AWS::LicenseManager::License: ProductSKU property is now required
aws-sagemaker: AWS::SageMaker::Cluster: Orchestrator.Eks property is now immutable
Features
Bug Fixes
ajvthat triggers CVE scanners (#37022) (45662ba)Alpha modules (2.239.0-alpha.0)
⚠ BREAKING CHANGES
redshift-alpha: update default node type from
DC2_LARGEtoRA3_LARGEFeatures
fromCodeAssetmethod to create runtime artifact with local code assets (#36472) (c5a87e6), closes #36473toDestination()(#36896) (48f1fe6)Bug Fixes
DC2_LARGEtoRA3_LARGE(#36516) (ea19e5c), closes #36416v2.238.0Compare Source
⚠ BREAKING CHANGES
Features
IDeliveryStreamRefas flow log destination (#36278) (cd73498), closes #33883 #34596 #33757Bug Fixes
Match.anyOfsupport for raw strings (#36908) (6804c7c), closes #36902 #36602 #36602Miscellaneous Chores
Alpha modules (2.238.0-alpha.0)
Features
Bug Fixes
MixinApplicator(#36877) (09db1c9), closes #36847v2.237.1Compare Source
Bug Fixes
Alpha modules (2.237.1-alpha.0)
v2.237.0Compare Source
⚠ BREAKING CHANGES
IEncryptedResourceobjects now have fewer guarantees about the shape of the object. If you still require anIResource, change the type toIEncryptedResource & IResourceand/or add a type guard check usingResource.isResource(). Implementations ofIEncryptedResourceno longer need to implementIResourcebut must continue to implementIEnvironmentAware. SinceIResourceextendsIEnvironmentAware, there is no change for implementors. Calls toGrantableResources.isEncryptedResource()now require anIEnvironmentAwareargument instead ofIConstruct.Features
trustAccountIdentitiesoptional inKeyGrants(#36786) (06676ac)Configuration
📅 Schedule: (in timezone America/Chicago)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.