CSRF protection was not present in SquaredUp before version 4.6.0. A CSRF attack could have been possible by an administrator executing arbitrary code in a HTML dashboard tile via a crafted HTML page, or by uploading a malicious SVG payload into a dashboard.
References
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 05:40
Type | Values Removed | Values Added |
---|---|---|
References | () https://scomsupport.squaredup.com/hc/en-us/articles/8862921957533-CVE-2020-9388-API-Endpoints-are-not-protected-against-CSRF - | |
References | () https://support.squaredup.com/hc/en-us/articles/360017568238 - Broken Link, Vendor Advisory | |
References | () https://support.squaredup.com/hc/en-us/articles/360019427218-CVE-2020-9388-API-Endpoints-are-not-protected-against-CSRF - Broken Link, Vendor Advisory |
Information
Published : 2021-02-03 20:15
Updated : 2024-11-21 05:40
NVD link : CVE-2020-9388
Mitre link : CVE-2020-9388
CVE.ORG link : CVE-2020-9388
JSON object : View
Products Affected
squaredup
- squaredup
CWE
CWE-352
Cross-Site Request Forgery (CSRF)