CVE-2024-28056

Published Apr 15, 2024 CVSS 3.1 · 9.8 Critical EPSS 1.7% KEV · Not listed
Description
Amazon AWS Amplify CLI before 12.10.1 incorrectly configures the role trust policy of IAM roles associated with Amplify projects. When the Authentication component is removed from an Amplify project, a Condition property is removed but "Effect":"Allow" remains present, and consequently sts:AssumeRoleWithWebIdentity would be available to threat actors with no conditions. Thus, if Amplify CLI had been used to remove the Authentication component from a project built between August 2019 and January 2024, an "assume role" may have occurred, and may have been leveraged to obtain unauthorized access to an organization's AWS resources. NOTE: the problem could only occur if an authorized AWS user removed an Authentication component. (The vulnerability did not give a threat actor the ability to remove an Authentication component.) However, in realistic situations, an authorized AWS user may have removed an Authentication component, e.g., if the objective were to stop using built-in Cognito resources, or move to a completely different identity provider.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2024-1151 Amazon AWS Amplify CLI before 12.10.1 incorrectly configures the role trust policy of IAM roles associated with Amplify projects. When the Authentication component is removed from an Amplify project, a Condition property is removed but "Effect":"Allow" remains present, and consequently sts:AssumeRoleWithWebIdentity would be available to threat actors with no conditions. Thus, if Amplify CLI had been used to remove the Authentication component from a project built between August 2019 and January 2024, an "assume role" may have occurred, and may have been leveraged to obtain unauthorized access to an organization's AWS resources. NOTE: the problem could only occur if an authorized AWS user removed an Authentication component. (The vulnerability did not give a threat actor the ability to remove an Authentication component.) However, in realistic situations, an authorized AWS user may have removed an Authentication component, e.g., if the objective were to stop using built-in Cognito resources, or move to a completely different identity provider.
Github GHSA Github GHSA GHSA-846g-p7hm-f54r AWS Amplify CLI has incorrect trust policy management
History
Type Values Removed Values Added
First Time appeared Amazon aws Amplify Cli
CPEs cpe:2.3:a:amazon:amplify_cli:*:*:*:*:*:aws:*:* cpe:2.3:a:amazon:aws_amplify_cli:*:*:*:*:*:-:*:*
Vendors & Products Amazon amplify Cli
Amazon aws Amplify Cli
Type Values Removed Values Added
Metrics epss

{'score': 0.00427}

epss

{'score': 0.00452}

Type Values Removed Values Added
First Time appeared Amazon
Amazon amplify Cli
CPEs cpe:2.3:a:amazon:amplify_cli:*:*:*:*:*:aws:*:*
Vendors & Products Amazon
Amazon amplify Cli
Type Values Removed Values Added
First Time appeared Aws
Aws amplify Cli
Weaknesses CWE-276
CPEs cpe:2.3:a:aws:amplify_cli:*:*:*:*:*:*:*:*
Vendors & Products Aws
Aws amplify Cli
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Mar 20, 2025, 6:58 PM
Reserved
Mar 1, 2024, 12:00 AM
Status
Analyzed
Published
Apr 15, 2024, 6:15 PM
Modified
Sep 4, 2026, 2:13 PM