Cross-site scripting via inadequately neutralized component content
Published Feb 24, 2022 · Updated Apr 23, 2025
Cross-site scripting in Amazon Web Services @awsui/components-react before 3.0.367 allows remote attackers to inject JavaScript into rendered content. Multiple components render user-controlled content without adequate neutralization, but the maintainer has not identified the affected components or input properties. Exploitation requires a user to render attacker-controlled content and allows script execution in the consuming web application's browser context.
Summary
What happened
Cross-site scripting in Amazon Web Services @awsui/components-react before 3.0.367 allows remote attackers to inject JavaScript into rendered content. Multiple components render user-controlled content without adequate neutralization, but the maintainer has not identified the affected components or input properties. Exploitation requires a user to render attacker-controlled content and allows script execution in the consuming web application's browser context.
The record
- CVE
- CVE-2022-24709
- Published
- Feb 24, 2022
- Updated
- Apr 23, 2025
- Vendor
- Amazon Web Services
- Product
- AWS UI Documentation
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 24, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=< 3.0.367
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