Authenticated browser code execution via user information update
Published Apr 29, 2020 · Updated Aug 4, 2024
Cross-site scripting in IFRN SUAP 2.0 allows remote authenticated users to execute browser code through a user-information update. Public records identify the user-information update flow but do not disclose the affected field or the missing output-encoding operation. A low-privileged account and user interaction are required; successful exploitation exposes or alters data available to the affected browser session.
Summary
What happened
Cross-site scripting in IFRN SUAP 2.0 allows remote authenticated users to execute browser code through a user-information update. Public records identify the user-information update flow but do not disclose the affected field or the missing output-encoding operation. A low-privileged account and user interaction are required; successful exploitation exposes or alters data available to the affected browser session.
The record
- CVE
- CVE-2019-7634
- Published
- Apr 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 29, 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
- CVE-2019–7634 My first CVEproof 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