{"id":"EUVD-2024-1151","revision":null,"records":[{"revision":"ec9b73c3608b424488678e3927d36229","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2024-28056","aliases":[],"title":"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 \"Eff…","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.","state":0,"publishedAt":"2024-04-15T00:00:00+00:00","modifiedAt":"2025-03-20T18:58:39.089+00:00","affected":[{"ecosystem":"Vendor product","name":"n/a","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"n/a\",\n                    \"product\": \"n/a\",\n                    \"versions\": [\n                        {\n                            \"version\": \"n/a\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[],"references":["https://github.com/aws-amplify/amplify-cli/releases/tag/v12.10.1","https://github.com/aws-amplify/amplify-cli/commit/73b08dc424db2fb60399c5343c314e02e849d4a1","https://github.com/aws-amplify/amplify-cli/blob/8ad57bf99a404f3c92547c8a175458016f682fac/packages/amplify-provider-awscloudformation/resources/update-idp-roles-cfn.json","https://securitylabs.datadoghq.com/articles/amplified-exposure-how-aws-flaws-made-amplify-iam-roles-vulnerable-to-takeover/","https://aws.amazon.com/security/security-bulletins/AWS-2024-003/"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2024-28056","license":"CVE Program Terms of Use","key":"cve-program:CVE-2024-28056","identifiers":["CVE-2024-28056"]},"retained":false,"historicalAffected":[]},{"revision":"c4182641cd2a4d8eb5920e86a96082e8","observedAt":"2026-11-19T03:30:07.796+00:00","statement":{"source":"euvd","id":"EUVD-2024-1151","aliases":["CVE-2024-28056","GHSA-846g-p7hm-f54r"],"title":"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 \"Eff…","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.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","score":9.8,"severity":null}],"references":["https://github.com/aws-amplify/amplify-cli/releases/tag/v12.10.1","https://github.com/aws-amplify/amplify-cli/commit/73b08dc424db2fb60399c5343c314e02e849d4a1","https://github.com/aws-amplify/amplify-cli/blob/8ad57bf99a404f3c92547c8a175458016f682fac/packages/amplify-provider-awscloudformation/resources/update-idp-roles-cfn.json","https://securitylabs.datadoghq.com/articles/amplified-exposure-how-aws-flaws-made-amplify-iam-roles-vulnerable-to-takeover/","https://aws.amazon.com/security/security-bulletins/AWS-2024-003/"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2024-1151","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"Apr 15, 2024, 12:00:00 AM","dateUpdated":"Mar 20, 2025, 6:58:39 PM"},"relatedAdvisories":[],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2024-1151","identifiers":["EUVD-2024-1151","CVE-2024-28056","GHSA-846g-p7hm-f54r"]},"retained":false,"historicalAffected":[]},{"revision":"6d04a2a914cf4f869c32f53c7a3bc630","observedAt":"2026-10-24T23:17:28.568+00:00","statement":{"source":"nvd","id":"CVE-2024-28056","aliases":[],"title":"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 \"Eff…","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.","state":0,"publishedAt":"2024-04-15T18:15:10.723+00:00","modifiedAt":"2026-09-04T14:13:32.82+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","score":9.8,"severity":"CRITICAL"}],"references":["https://aws.amazon.com/security/security-bulletins/AWS-2024-003/","https://github.com/aws-amplify/amplify-cli/blob/8ad57bf99a404f3c92547c8a175458016f682fac/packages/amplify-provider-awscloudformation/resources/update-idp-roles-cfn.json","https://github.com/aws-amplify/amplify-cli/commit/73b08dc424db2fb60399c5343c314e02e849d4a1","https://github.com/aws-amplify/amplify-cli/releases/tag/v12.10.1","https://securitylabs.datadoghq.com/articles/amplified-exposure-how-aws-flaws-made-amplify-iam-roles-vulnerable-to-takeover/"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2024-28056","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Analyzed","weaknesses":["CWE-276"],"productCriteria":["cpe:2.3:a:amazon:aws_amplify_cli:*:*:*:*:*:-:*:*"],"sourceDates":{"published":"2024-04-15T18:15:10.723","lastModified":"2026-09-04T14:13:32.820"},"relatedAdvisories":[],"note":"NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON."},"key":"nvd:CVE-2024-28056","identifiers":["CVE-2024-28056"]},"retained":false,"historicalAffected":[]},{"revision":"83572fd34e694f1ca20c16f9541cc054","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"GHSA-846g-p7hm-f54r","aliases":["CVE-2024-28056"],"title":"AWS Amplify CLI has incorrect trust policy management","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.","state":0,"publishedAt":"2024-04-15T18:30:51+00:00","modifiedAt":"2024-08-15T21:38:29+00:00","affected":[{"ecosystem":"npm","name":"@aws-amplify/cli","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"12.10.1"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"CRITICAL"}],"references":["https://nvd.nist.gov/vuln/detail/CVE-2024-28056","https://github.com/aws-amplify/amplify-cli/commit/73b08dc424db2fb60399c5343c314e02e849d4a1","https://aws.amazon.com/security/security-bulletins/AWS-2024-003","https://github.com/aws-amplify/amplify-cli","https://github.com/aws-amplify/amplify-cli/blob/8ad57bf99a404f3c92547c8a175458016f682fac/packages/amplify-provider-awscloudformation/resources/update-idp-roles-cfn.json","https://github.com/aws-amplify/amplify-cli/releases/tag/v12.10.1","https://securitylabs.datadoghq.com/articles/amplified-exposure-how-aws-flaws-made-amplify-iam-roles-vulnerable-to-takeover"],"sourceUrl":"https://github.com/advisories/GHSA-846g-p7hm-f54r","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-846g-p7hm-f54r","identifiers":["GHSA-846g-p7hm-f54r","CVE-2024-28056"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-19T15:01:21.3315545+00:00","complete":true,"records":1786,"lastAttemptAt":"2026-11-19T15:01:21.3315545+00:00","lastSuccessAt":"2026-11-19T15:01:21.5019314+00:00","error":null,"lastVerifiedAt":"2026-11-19T15:01:21.5019323+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-e55c589538e0700b45c7d6d41fe1447a79199283262c371c864535c791a040b9-d42c703c61cc3c6d1f760f4d087897ddb503f3bb8ab25df157835cf5a8fe3a94","complete":true,"records":428499,"lastAttemptAt":"2026-11-19T14:59:42.1428877+00:00","lastSuccessAt":"2026-11-19T14:59:42.0611368+00:00","error":null,"lastVerifiedAt":"2026-11-19T14:59:42.1428877+00:00","snapshotPublishedAt":"2026-11-19T14:29:09+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-26529f66dffa421bbc348eb3061d9236","complete":false,"records":13861,"lastAttemptAt":"2026-11-19T15:11:12.2316141+00:00","lastSuccessAt":"2026-11-19T15:11:12.227+00:00","error":"229 identifier lookups failed; latest failures include AccessDenied (HTTP 403). Other identifiers were checked independently.","lastVerifiedAt":"2026-11-19T15:11:12.227+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13679,"expectedIdentifiers":13908,"failedIdentifiers":229},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-19T15:01:21.3315545+00:00","complete":true,"records":1125,"lastAttemptAt":"2026-11-19T15:01:21.3315545+00:00","lastSuccessAt":"2026-11-19T15:01:21.5028737+00:00","error":null,"lastVerifiedAt":"2026-11-19T15:01:21.5028738+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-3d346fd985e841b1aac7f0b69a8e04b9","complete":true,"records":13873,"lastAttemptAt":"2026-11-19T15:01:35.3188656+00:00","lastSuccessAt":"2026-11-19T15:01:35.314+00:00","error":null,"lastVerifiedAt":"2026-11-19T15:01:35.314+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13908,"expectedIdentifiers":13908,"failedIdentifiers":0},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-76574c95b6792d47ba90af64983ed5843633f14426346d676016e94a5f383202","complete":true,"records":9963,"lastAttemptAt":"2026-11-19T15:01:21.1838445+00:00","lastSuccessAt":"2026-11-19T01:24:31.4213722+00:00","error":null,"lastVerifiedAt":"2026-11-19T15:01:21.1838445+00:00","snapshotPublishedAt":"2026-11-19T01:03:15+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-f4424d7d4861b1af1404bd15abcb83f295dcd003412a9340ca99dc8200aa148a","complete":true,"records":2014,"lastAttemptAt":"2026-11-19T14:59:42.2842727+00:00","lastSuccessAt":"2026-11-13T19:57:08.2864435+00:00","error":null,"lastVerifiedAt":"2026-11-19T14:59:42.2842727+00:00","snapshotPublishedAt":"2026-11-13T19:33:10+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-313d8afdba3867de110bc2f0cc252c7b787cb94e08a055d09b0542017e147ca8","complete":true,"records":3194,"lastAttemptAt":"2026-11-19T15:01:21.2884267+00:00","lastSuccessAt":"2026-11-19T09:40:31.5988269+00:00","error":null,"lastVerifiedAt":"2026-11-19T15:01:21.2884267+00:00","snapshotPublishedAt":"2026-11-19T09:03:08+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-723a433246e9cdaa22cd2b5cabd24a20f0024f418c34c5e5569e1f788454d859","complete":true,"records":232738,"lastAttemptAt":"2026-11-19T15:01:21.0564094+00:00","lastSuccessAt":"2026-11-19T15:01:20.0364127+00:00","error":null,"lastVerifiedAt":"2026-11-19T15:01:21.0564094+00:00","snapshotPublishedAt":"2026-11-19T14:33:12+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}