Exploitation status
KEV status unavailable
The KEV source did not return a conclusive status.
Opening Forensia workspaceacquiring
Loading the current evidence view. Navigation and account controls remain available.
Loading recent evidenceacquiring
Indicator investigation
Loading the current evidence view. Navigation and account controls remain available.
Loading verdict, provenance, relationships and sightings.
Indicator
Type cve · source NVD CVE
CRITICAL SEVERITY (CVSS 9.8)
Vulnerability investigation
CISA KEV status could not be verified from the available evidence. NVD rates the technical severity critical at CVSS 9.8. These are public vulnerability signals, not proof that a specific environment runs an affected version.
Exploitation status
KEV status unavailable
The KEV source did not return a conclusive status.
30-day exploitation likelihood
Unavailable
FIRST EPSS did not return a score.
Technical severity
9.8 · critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected surface
1 parsed product
Amazon Aws Amplify Cli
Weakness class
CWE-276
CWE describes the weakness category, not whether a deployed product is reachable or exploitable.
Corpus evidence
1 connectors · 1 citations
No related report text is available in the local corpus.
Findings stay bounded to named sources and observable infrastructure.
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.
The base CVE appears first. Independent evidence is added without blocking the page.
Investigation status
Checking for newly completed evidence
NIST NVD
NVD evidence is available in this response
CISA KEV
Known-exploitation catalog check is pending
FIRST EPSS
Forensia does not request or publish EPSS while source rights are under review
Reports
Report links are still being resolved
Relationships
Product and vulnerability relationships are still being prepared
Vendor/product strings parsed from local CPE URIs (no inferred ATT&CK).
| Product | CPE (truncated) |
|---|---|
| Amazon Aws Amplify Cli | cpe:2.3:a:amazon:aws_amplify_cli:*:*:*:*:*:-:*:* |
Neighborhood topology. Open the graph for interactive pivots.
Loading connected indicators, reports and entities.
High-signal pivots without leaving the thread you started in search.
Structured pivots from local graph context.
Full investigation canvas with neighbor expansion.