Browser script execution via DEVICE_NAME injection
Published Jan 13, 2020 · Updated Aug 4, 2024
Cross-site scripting in Axper Vision II 4 firmware 4.1.53.166 allows remote attackers to run script in an operator's browser. The configWebParams.cgi handler renders attacker-controlled DEVICE_NAME input as web-page content without the required neutralization. Exploitation requires an operator to load the affected content; execution remains in the browser context and enables data reads or actions with that operator's access.
Summary
What happened
Cross-site scripting in Axper Vision II 4 firmware 4.1.53.166 allows remote attackers to run script in an operator's browser. The configWebParams.cgi handler renders attacker-controlled DEVICE_NAME input as web-page content without the required neutralization. Exploitation requires an operator to load the affected content; execution remains in the browser context and enables data reads or actions with that operator's access.
The record
- CVE
- CVE-2020-6848
- Published
- Jan 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 2020CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- sku11army Vision II XSS disclosureproof 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