CVE-2017-18362

CRITICAL9.8

CISA KEV

Published 2019-02-05 · Updated 2026-08-13 · Source cve@mitre.org

Summary

CVE-2017-18362 is a critical-severity (CVSS 9.8) vulnerability in Kaseya Virtual System/Server Administrator (VSA). CISA added it to the Known Exploited Vulnerabilities catalog on May 24, 2022, which means exploitation in the wild has been confirmed; US federal agencies had to remediate it by June 14, 2022. CISA also lists it as known to be used in ransomware campaigns, so it should be prioritised accordingly. Kaseya has 3 vulnerabilities in the KEV catalog, 3 of them linked to ransomware.

All 3 known-exploited Kaseya vulnerabilities →

Description

ConnectWise ManagedITSync integration through 2017 for Kaseya VSA is vulnerable to unauthenticated remote commands that allow full direct access to the Kaseya VSA database. In February 2019, attackers have actively exploited this in the wild to download and execute ransomware payloads on all endpoints managed by the VSA server. If the ManagedIT.asmx page is available via the Kaseya VSA web interface, anyone with access to the page is able to run arbitrary SQL queries, both read and write, without authentication.

CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE-89CWE-89

CISA Known-Exploited Vulnerability

Product: Kaseya — Virtual System/Server Administrator (VSA)

Name: Kaseya VSA SQL Injection Vulnerability

Date added: 2022-05-24 · Due: 2022-06-14

USED IN RANSOMWARE

Required action: The impacted product is end-of-life and should be disconnected if still in use.

References

View on NVD

More exploited Kaseya vulnerabilities

Most recently added to CISA KEV

CVE-2018-20753
RANSOMWARE
Virtual System/Server Administrator (VSA) — Kaseya VSA Remote Code Execution Vulnerability
added 2022-04-13
CVE-2021-30116
RANSOMWARE
Virtual System/Server Administrator (VSA) — Kaseya Virtual System/Server Administrator (VSA) Information Disclosure Vulnerability
added 2021-11-03

View all →

Related CVEs

Same severity, most recent

CVE-2026-109469
Authorization bypass through user-controlled key in Entra Device Registration allows an unauthorized attacker to elevate privileges over a network.
2026-11-06 · score 10.0
CVE-2026-68935
Chartbrew is an open-source web application for creating charts from databases and APIs. In versions 4.8.5 through 5.2.2, API connection creation and update operations accept the internal allowPrivateHost field from user input. An authenticated user with permission to manage API connections can enable this field to bypass private and reserved-network destination restrictions. An upgrade migration also enables the override on pre-existing API connections. The per-connection setting takes precedence over CB_ALLOW_PRIVATE_NETWORK_CALLS , so disabling that instance option does not protect connections with the override enabled. Successful exploitation allows requests to internal HTTP services reachable from the Chartbrew server, potentially disclosing information or triggering unauthorized actions depending on the target service. Recognized cloud metadata endpoints remain separately blocked. This issue is fixed in version 5.2.3.
2026-11-06 · score 9.1
CVE-2026-59104
UgCS server before 6.2 contains an authentication bypass in the HCI protocol login handler (LoginHandler) exposed on TCP port 3334. When the user database contains exactly one user (the default single-operator installation), a LoginRequest with empty userLogin and userPassword fields is interpreted as \"use the only user\" rather than as invalid credentials, and the server returns a fully authenticated session. Because the service listens on all interfaces (0.0.0.0) without TLS by default, an unauthenticated remote attacker with network access to port 3334 can obtain an authenticated session without knowing any credential and then issue privileged commands, including commanding connected drones and uploading flight routes.
2026-11-06 · score 9.8
CVE-2026-86044
JupyterLab Desktop is the cross-platform desktop application for JupyterLab. Prior to 4.6.2-1, JupyterLab Desktop exposed getServerInfo to the renderer without confirming that the current page still had the local Jupyter server origin. In a local managed session using JupyterLab before 4.4.8, an attacker can place a crafted MathJax link in an untrusted notebook. If a victim opens the notebook and clicks the link, the existing renderer navigates to an attacker-controlled site while retaining access to the preload bridge. The site can call getServerInfo to obtain the local server URL and authentication token, then use the Jupyter REST API to create and trust a notebook that executes arbitrary code as the victim. Users whose environment already uses JupyterLab 4.4.8 or later are unaffected because the corrected link handling breaks the first step of the chain. This vulnerability is fixed in 4.6.2-1.
2026-11-06 · score 9.6
CVE-2026-85295
Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.3, four authentication helpers accepted session tokens signed with CB_SECRET, including known, weak, or shipped-default values. The vulnerable surface is session JWT fallback in server/modules/verifyToken.js, verifyUser.js, getUserFromToken.js, and socketManager.js across the API and socket layer. A stock source or repository Docker Compose deployment retains a known, weak, or default CB_SECRET and an attacker submits a forged HS256 token decoding to a target user id. Knowing the symmetric secret lets the attacker create a token that the legacy verification fallback accepts as the target user without that user's password or two-factor authentication. The condition includes stock source and repository Docker Compose installs and any otherwise known or weak CB_SECRET; a bare container where CB_SECRET is undefined is not affected by this fallback path. A forged session impersonates the chosen user across the entire API and socket layer and exercises that user's Chartbrew privileges. This issue is fixed in version 5.2.3.
2026-11-06 · score 9.8