# CVE-2017-18362: Kaseya VSA SQL Injection

> Unauthenticated attackers can execute arbitrary SQL queries via the ManagedITSync integration, leading to database access and remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 24 May 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2019
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-w35f-w5cg-jqhh

## What is CVE-2017-18362?

CVE-2017-18362 is a critical SQL injection vulnerability in n/a, published on 5 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2017-18362?

It affects 1 product.


Products: Connectwise Manageditsync.

## How do I fix CVE-2017-18362?

No fix has been published for CVE-2017-18362 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 14 Jun 2022.

## Is CVE-2017-18362 being exploited?

Yes. Attackers have exploited CVE-2017-18362 in the wild since at least 24 May 2022, including in ransomware campaigns.

Public exploit code:

- Kaseya VSA 2017 ConnectWise ManagedITSync - Remote Code Execution (nuclei): http/cves/2017/CVE-2017-18362.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18362 and fix it if it is affected.

What it is: CVE-2017-18362 is a critical SQL injection vulnerability in n/a, published on 5 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-18362 in the wild since at least 24 May 2022, including in ransomware campaigns.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-18362/ (Markdown: https://insights.sbomify.com/CVE-2017-18362/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-18362
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-18362
- OSV: https://osv.dev/vulnerability/CVE-2017-18362

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-18362/
Summaries are generated and may contain mistakes; the official description above is the record.