Stored script execution via update filename
Published Jan 8, 2021 · Updated Aug 4, 2024
Stored XSS in Innokas VC150 Vital Signs Monitor firmware before 1.7.15 allows remote authenticated users to execute script via an update filename. Multiple administrative update endpoints store the filename parameter without neutralizing embedded web script or HTML before rendering it. An authenticated attacker must submit the filename and an administrator must later view the stored value, enabling script execution in that trusted browser session.
Summary
What happened
Stored XSS in Innokas VC150 Vital Signs Monitor firmware before 1.7.15 allows remote authenticated users to execute script via an update filename. Multiple administrative update endpoints store the filename parameter without neutralizing embedded web script or HTML before rendering it. An authenticated attacker must submit the filename and an administrator must later view the stored value, enabling script execution in that trusted browser session.
The record
- CVE
- CVE-2020-27262
- Published
- Jan 8, 2021
- Updated
- Aug 4, 2024
- Vendor
- Innokas
- Product
- VC150 Vital Signs Monitor
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 8, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=VC150 prior to Version 1.7.15
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