Authenticated script execution via undisclosed HTML injection
Published Aug 25, 2022 · Updated Aug 3, 2024
HTML injection in Archer Platform 6.x before 6.11 P3 allows remote authenticated users to execute script in a victim's browser. Public records do not identify the affected field, page, code path, or failed output-neutralization operation. Exploitation requires authenticated access and a victim application user to view or interact with attacker-controlled content.
Summary
What happened
HTML injection in Archer Platform 6.x before 6.11 P3 allows remote authenticated users to execute script in a victim's browser. Public records do not identify the affected field, page, code path, or failed output-neutralization operation. Exploitation requires authenticated access and a victim application user to view or interact with attacker-controlled content.
The record
- CVE
- CVE-2022-37317
- Published
- Aug 25, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 25, 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?
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
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