Amplify Studio: Improper Neutralization of Directives in Dynamically Evaluated Code
CVE-2025-4318 is a critical-severity improper neutralization of directives in dynamically evaluated code vulnerability in Amplify Studio from Amazon, with a CVSS 4.0 base score of 9.0 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 2.20.3 as the first without the flaw, so updating Amplify Studio to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.99% chance of exploitation within 30 days, higher than 63% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Amplify Studio to 2.20.3 or a later version.
- Read the advisory on aws.amazon.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Amazon | Amplify Studio | 0.1.0 up to, but not including, 2.20.3 | 2.20.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Attack requirements
- PresentThe target must be in a specific state or configuration for the attack to work.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Confidentiality (vulnerable system)
- HighSerious loss of confidentiality on the vulnerable system.
- Integrity (vulnerable system)
- HighSerious loss of integrity on the vulnerable system.
- Availability (vulnerable system)
- HighSerious loss of availability on the vulnerable system.
- Confidentiality (other systems)
- HighSerious loss of confidentiality on systems beyond the vulnerable one.
- Integrity (other systems)
- HighSerious loss of integrity on systems beyond the vulnerable one.
- Availability (other systems)
- HighSerious loss of availability on systems beyond the vulnerable one.
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. Scored by CNA.
Official description
The AWS Amplify Studio UI component property expressions in the aws-amplify/amplify-codegen-ui package lack input validation. This could potentially allow an authenticated user who has access to create or modify components to run arbitrary JavaScript code during the component rendering and build process.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Directives in Dynamically Evaluated Code
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. eval).
How developers prevent this class of flaw
- If possible, refactor your code so that it does not need to use eval() at all.
- For Python programs, it is frequently encouraged to use the ast.literal_eval() function instead of eval, since it is intentionally designed to avoid executing code. However, an adversary could still cause excessive memory or stack consumption via deeply nested structures, so the python documentation discourages use of ast.literal_eval() on untrusted data.
More Improper Neutralization of Directives in Dynamically Evaluated Code vulnerabilities (CWE-95)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Patches and release notes
Other references
Recent Improper Neutralization of Directives in Dynamically Evaluated Code vulnerabilities
- 9.1 Critical severity
- 9.3 Critical severity
- 7.3 High severity
- 9.1 Critical severity
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.