CVE-2017-18362
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedConnectWise 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUnauthenticated SQL injection vulnerability in the ManagedIT.asmx page of Kaseya VSA's ConnectWise ManagedITSync integration allows remote attackers to execute arbitrary SQL queries (read and write) against the VSA database without any authentication. Attackers exploited this in February 2019 to deploy ransomware across all endpoints managed by the compromised VSA server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2017CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if ManagedIT.asmx endpoint is presentSearch the Kaseya VSA web server directories for the ManagedIT.asmx file, typically found under paths like /ManagedITSync/ or /WebServices/ManagedIT.asmxAffected if The ManagedIT.asmx file exists on the server
-
Verify ConnectWise ManagedITSync integration is installedLook for ManagedITSync components in the Kaseya VSA installation directory, checking for related DLLs, configuration files, or services named ManagedITSyncAffected if The ManagedITSync integration components are installed on the Kaseya VSA server
-
Determine the ConnectWise ManagedITSync versionLocate version information in the ManagedITSync component files, assembly metadata, or within the Kaseya VSA admin interface under integration or plugin detailsAffected if The installed ManagedITSync version is 2017 or earlier
-
Confirm network accessibility of the vulnerable endpointVerify whether the ManagedIT.asmx web service is reachable from untrusted network segments or the internet by reviewing firewall rules, IIS bindings, and URL access controlsAffected if The ManagedIT.asmx endpoint is accessible from untrusted networks without authentication
A defender is affected if ConnectWise ManagedITSync version 2017 or earlier is installed with the ManagedIT.asmx endpoint present and accessible, allowing unauthenticated SQL injection attacks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately restrict network access to or disable the ManagedIT.asmx endpoint, apply available vendor patches or upgrade to a patched version, and review for signs of compromise given active in-the-wild exploitation.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18362 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-18362 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data