Lucene search
K

SugarCRM Cross Site Scripting

🗓️ 12 Aug 2020 00:00:00Reported by EgiXType 
packetstorm
 packetstorm
🔗 packetstormsecurity.com👁 181 Views

SugarCRM < 10.1.0 Multiple Reflected Cross-Site Scripting Vulnerabilities. User input not sanitized in "do" parameter, "current_step" parameter, and "updated_records" parameter

Related
Code
ReporterTitlePublishedViews
Family
CNVD
SugarCRM Cross-Site Scripting Vulnerability (CNVD-2020-46296)
14 Aug 202000:00
cnvd
CVE
CVE-2020-17372
12 Aug 202012:24
cve
Cvelist
CVE-2020-17372
12 Aug 202012:24
cvelist
EUVD
EUVD-2020-9326
7 Oct 202500:30
euvd
NVD
CVE-2020-17372
12 Aug 202013:15
nvd
Prion
Cross site scripting
12 Aug 202013:15
prion
RedhatCVE
CVE-2020-17372
22 May 202515:58
redhatcve
`SugarCRM < 10.1.0 Multiple Reflected Cross-Site Scripting Vulnerabilities  
  
*• Software Link:*  
  
https://www.sugarcrm.com/  
  
*• Affected Versions:*  
  
All versions prior to 10.1.0 (Q3 2020).  
  
*• Vulnerabilities Description:*  
  
1) User input passed through the “do” parameter when action is set to  
“metadata” is not properly sanitized before being used to generate HTML  
output. This can be exploited by malicious users to carry out Reflected  
Cross-Site Scripting (XSS) attacks.  
  
*• Proof of Concept 1:*  
  
https://[HOST]/index.php?action=metadata&do=%27);alert(%27XSS%27)//  
  
2) User input passed through the “current_step” parameter to the “Reports”  
module is not properly sanitized before being used to generate HTML output.  
This can be exploited by malicious users to carry out Reflected Cross-Site  
Scripting (XSS) attacks.  
  
*• Proof of Concept 2:*  
  
https://  
[HOST]/index.php?module=Reports&action=ReportsWizard&save_report=on&current_step=%22%3E%3Cimg%20src=x%20onerror=alert(%22XSS%22)%3E  
  
3) User input passed through the “updated_records” parameter is not  
properly sanitized before being used to generate HTML output. This can be  
exploited by malicious users to carry out Reflected Cross-Site Scripting  
(XSS) attacks.  
  
*• Proof of Concept 3:*  
  
https://  
[HOST]/index.php?updated_records=%3Cimg%20src=x%20onerror=alert(/XSS/)%3E  
  
*• Solution:*  
  
Upgrade to version 10.1.0 (Q3 2020) or later.  
  
*• Disclosure Timeline:*  
  
[05/02/2020] – Vendor notified  
[06/02/2020] – Automoatic vendor response received  
[26/03/2020] – Vendor contacted again; no response  
[17/04/2020] – Vendor contacted again; no response  
[18/06/2020] – Vendor nodified about a 180-day disclosure deadline  
[03/08/2020] – After around 180 days the vendor silently fix the issue  
[06/08/2020] – CVE number assigned  
[10/08/2020] – Public disclosure  
  
*• CVE Reference:*  
  
The Common Vulnerabilities and Exposures project (cve.mitre.org)  
has assigned the name CVE-2020-17372  
<http://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-17372> to these  
vulnerabilities.  
  
*• Credits:*  
  
Vulnerabilities discovered by Egidio Romano.  
  
  
`

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation

12 Aug 2020 00:00Current
5.6Medium risk
Vulners AI Score5.6
EPSS0.00493
181