CVE-2023-23127
https://notcve.org/view.php?id=CVE-2023-23127
In Connectwise Control 22.8.10013.8329, the login page does not implement HSTS headers therefore not enforcing HTTPS. NOTE: the vendor's position is that, by design, this is controlled by a configuration option in which a customer can choose to use HTTP (rather than HTTPS) during troubleshooting. • https://github.com/l00neyhacker/CVE-2023-23127 • CWE-311: Missing Encryption of Sensitive Data •
CVE-2023-23128
https://notcve.org/view.php?id=CVE-2023-23128
Connectwise Control 22.8.10013.8329 is vulnerable to Cross Origin Resource Sharing (CORS). The vendor's position is that two endpoints have Access-Control-Allow-Origin wildcarding to support product functionality, and that there is no risk from this behavior. The vulnerability report is thus not valid. • https://github.com/l00neyhacker/CVE-2023-23128 •
CVE-2021-32582
https://notcve.org/view.php?id=CVE-2021-32582
An issue was discovered in ConnectWise Automate before 2021.5. A blind SQL injection vulnerability exists in core agent inventory communication that can enable an attacker to extract database information or administrative credentials from an instance via crafted monitor status responses. Se ha detectado un problema en ConnectWise Automate versiones anteriores a 2021.5. Se presenta una vulnerabilidad de inyección SQL ciega en la comunicación del inventario del agente principal que puede permitir a un atacante extraer información de la base de datos o credenciales administrativas de una instancia por medio de respuestas de estado de monitorización diseñadas • https://home.connectwise.com/securityBulletin/609a9dd75cb8450001e85369 https://www.connectwise.com/company/trust/security-bulletins https://www.connectwise.com/platform/unified-management/automate • CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') •
CVE-2020-15008
https://notcve.org/view.php?id=CVE-2020-15008
A SQLi exists in the probe code of all Connectwise Automate versions before 2020.7 or 2019.12. A SQL Injection in the probe implementation to save data to a custom table exists due to inadequate server side validation. As the code creates dynamic SQL for the insert statement and utilizes the user supplied table name with little validation, the table name can be modified to allow arbitrary update commands to be run. Usage of other SQL injection techniques such as timing attacks, it is possible to perform full data extraction as well. Patched in 2020.7 and in a hotfix for 2019.12. • https://slagle.tech/2020/07/06/cve-2020-15008 • CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') •