aws-cdk
Affected
- introduced
2.142.0, fixed2.148.1(semver)
Fixed versions
2.148.1
Fix
- Fixed version
2.148.1npm install [email protected]
Advisory
Also known as: CVE-2024-45037
AWS CDK RestApi not generating authorizationScope correctly in resultant CFN template
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
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 [[email protected]](mailto:[email protected]). Please do not create a public GitHub issue.
[1] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting
Medium Basis: The source's own band: MODERATE
2.142.0, fixed 2.148.1 (semver)2.148.1
2.148.1npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0