Cluster privilege escalation via account-root role trust
Published Jun 23, 2023 · Updated Dec 5, 2024
Incorrect authorization in AWS CDK EKS constructs before 1.202.0 or 2.80.0 allows remote authenticated users to gain elevated cluster access. The Cluster and FargateCluster constructs assign the AWS account root principal to CreationRole and default MastersRole trust policies. An in-account identity with sts:AssumeRole permission can assume those roles; MastersRole exposure also requires omission of the mastersRole property.
Summary
What happened
Incorrect authorization in AWS CDK EKS constructs before 1.202.0 or 2.80.0 allows remote authenticated users to gain elevated cluster access. The Cluster and FargateCluster constructs assign the AWS account root principal to CreationRole and default MastersRole trust policies. An in-account identity with sts:AssumeRole permission can assume those roles; MastersRole exposure also requires omission of the mastersRole property.
The record
- CVE
- CVE-2023-35165
- Published
- Jun 23, 2023
- Updated
- Dec 5, 2024
- Vendor
- Amazon Web Services
- Product
- AWS CDK CLI
- Classifications
- CWE-266, T1548.005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 23, 2023CVE publishedPublication date reported by the CVE source.
- Dec 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=@aws-cdk/aws-eks >= 1.57.0, < 1.202.0
- Affected versionversion=aws-cdk-lib >= 2.0.0, < 2.80.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo