Stored script execution via unsanitized flow names
Published Jan 28, 2020 · Updated Aug 5, 2024
Stored XSS in Node-RED 0.20.7 and earlier allows remote authenticated users to execute JavaScript in another editor user's browser. The editor fails to sanitize a new Flow's name field before rendering it, so a persisted HTML or script payload executes when another user views the flow. The attacker needs flow-write access and a victim must open the affected editor content; execution can expose session cookies or alter displayed content.
Summary
What happened
Stored XSS in Node-RED 0.20.7 and earlier allows remote authenticated users to execute JavaScript in another editor user's browser. The editor fails to sanitize a new Flow's name field before rendering it, so a persisted HTML or script payload executes when another user views the flow. The attacker needs flow-write access and a victim must open the affected editor content; execution can expose session cookies or alter displayed content.
The record
- CVE
- CVE-2019-15607
- Published
- Jan 28, 2020
- Updated
- Aug 5, 2024
- Vendor
- Node-RED
- Product
- Node-RED
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 28, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 2024Record 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=0.20.7 and earlier
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
- Stored flow-name XSS proof of conceptproof of concept · unverified
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