Persistent XSS via unvalidated charge-box ID
Published Aug 12, 2024 · Updated Aug 12, 2024
Stored XSS in SteVe before 3.5.1, 3.6.0, and 3.7.0 allows remote attackers to inject script through WebSocket charge-box IDs. OcppWebSocketHandshakeHandler accepted the final WebSocket URL segment as chargeBoxId without applying ChargeBoxIdValidator before storing and rendering it. A management-interface user must view the stored identifier, which executes attacker-supplied HTML or JavaScript in that user's browser and permits page-content access or modification.
Summary
What happened
Stored XSS in SteVe before 3.5.1, 3.6.0, and 3.7.0 allows remote attackers to inject script through WebSocket charge-box IDs. OcppWebSocketHandshakeHandler accepted the final WebSocket URL segment as chargeBoxId without applying ChargeBoxIdValidator before storing and rendering it. A management-interface user must view the stored identifier, which executes attacker-supplied HTML or JavaScript in that user's browser and permits page-content access or modification.
The record
- CVE
- CVE-2024-21550
- Published
- Aug 12, 2024
- Updated
- Aug 12, 2024
- Vendor
- SteVe Community
- Product
- SteVe
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 2024CVE publishedPublication date reported by the CVE source.
- Aug 12, 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 <3.5.1
- Affected versionversion=3.6.0 <3.6.1
- Affected versionversion=3.7.0 <3.7.1
What conditions does exploitation require?
What is affected?
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