Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency aws-cdk to v2.148.1 [SECURITY] #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 3, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
aws-cdk (source) 2.147.2 -> 2.148.1 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2024-45037

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.

We identified an issue in AWS Cloud Development Kit (CDK) which, under certain conditions, can result in granting authenticated Amazon Cognito users broader than intended access. Specifically, if a CDK application uses the "RestApi" construct with "CognitoUserPoolAuthorizer" as the authorizer and uses authorization scopes to limit access. This issue does not affect the availability of the specific API resources.

Impact

Authenticated Cognito users may gain unintended access to protected API resources or methods, leading to potential data disclosure, and modification issues.

Impacted versions: >=2.142.0;<=2.148.0

Patches

The patch is included in CDK version >=2.148.1.

Recommended Actions

  • Upgrade your AWS CDK version to 2.148.1 or newer and re-deploy your application(s) to address this issue.
  • If you are using older CDK versions before 2.142.0, you are not affected by this issue, however it is recommended to upgrade to the latest version to receive the latest features and fixes.
  • Confirm whether your application(s) is affected by searching for "CognitoUserPoolsAuthorizer" in your CDK application. If it is referenced inside the "RestApi" construct, and the "RestApi" resource or method utilize authorization scopes to limit access, and you deployed your applications using the impacted versions of CDK, your application is affected.

References

If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [1] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.

[1] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting


Release Notes

aws/aws-cdk (aws-cdk)

v2.148.1

Compare Source

Bug Fixes
  • apigateway: authorization scope is not added when not explicitly defining authorization type in method or root api (#​30822) (4bee768), closes #​30444

Alpha modules (2.148.1-alpha.0)

v2.148.0

Compare Source

Features
Bug Fixes
Reverts

Alpha modules (2.148.0-alpha.0)
Features
Bug Fixes

v2.147.3

Compare Source

Bug Fixes

Alpha modules (2.147.3-alpha.0)


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants