Browser script execution via unencoded login errors
Published Mar 11, 2020 · Updated Aug 5, 2024
Reflected XSS in Abacus OAuth Login 2018 before R6 and 2019 before R4 allows remote attackers to execute script through failed login errors. The /oauth/oauth2/v1/saml/ endpoint inserts a user-specified failed-login error message into its HTML response without output encoding. A victim must open the crafted request; script then runs in the vulnerable origin, and 2018 is affected only with AbaWebserver (Jetty), not AbaSioux.
Summary
What happened
Reflected XSS in Abacus OAuth Login 2018 before R6 and 2019 before R4 allows remote attackers to execute script through failed login errors. The /oauth/oauth2/v1/saml/ endpoint inserts a user-specified failed-login error message into its HTML response without output encoding. A victim must open the crafted request; script then runs in the vulnerable origin, and 2018 is affected only with AbaWebserver (Jetty), not AbaSioux.
The record
- CVE
- CVE-2019-19381
- Published
- Mar 11, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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
- Compass Security crafted failed-login error demonstrationproof of concept · demonstrated
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