Script execution via unsafe viewer navigation controls
Published Sep 8, 2022 · Updated Aug 3, 2024
Cross-site scripting in draw.io before 20.3.0 allows remote attackers to execute script in a victim's browser via unspecified vectors. The 20.3.0 changelog identifies the viewer back and refresh buttons as the affected locus, but the public patch does not disclose which untrusted value reaches the unsafe scripting sink. The two published assessments disagree on user interaction; successful execution is bounded to the draw.io browser origin and its origin-accessible data.
Summary
What happened
Cross-site scripting in draw.io before 20.3.0 allows remote attackers to execute script in a victim's browser via unspecified vectors. The 20.3.0 changelog identifies the viewer back and refresh buttons as the affected locus, but the public patch does not disclose which untrusted value reaches the unsafe scripting sink. The two published assessments disagree on user interaction; successful execution is bounded to the draw.io browser origin and its origin-accessible data.
The record
- CVE
- CVE-2022-3148
- Published
- Sep 8, 2022
- Updated
- Aug 3, 2024
- Vendor
- draw.io Ltd
- Product
- draw.io
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=unspecified <20.3.0
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
- Huntr.dev 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