Skip to content

CVE-2017-18362

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
9.8Criticalscored by CISA
Exploited in the wild
Yes, in CISA KEV since 24 May 2022CISA deadline for US federal agencies: 14 Jun 2022known use in ransomware campaigns
EPSS
86.8%chance of exploitation in the next 30 daystop 0.3% of scored CVEsFIRST score of 11 Nov 2026
Fix
Not stated by the vendorno fixed release in the CVE record
Published
5 Feb 2019analysed here 12 Nov 2026

Do first. The impacted product is end-of-life and should be disconnected if still in use. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
Yes. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • connectwise:manageditsync

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Yes. SQL injection puts SQL syntax into a request parameter, and WAF signatures recognise that syntax well.

Also consider: parameterized queries · ORM

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 24 May 2022. Known use in ransomware campaigns.
CISA due date
14 Jun 2022, the remediation deadline for US federal agencies
CISA required action
The impacted product is end-of-life and should be disconnected if still in use.
Public exploit code
Detection templates only, no public exploit found: 1 Nuclei template
CISA SSVC
exploitation active, automatable yes, technical impact totalAssessed by CISA 1 Jul 2022 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 5 Feb 2019Published
  2. 24 May 2022Added to CISA KEV (exploited in the wild)1,204 days (about 3 years) later
  3. 14 Jun 2022CISA remediation due date (US federal agencies)21 days later
  4. 1 Jul 2022CISA SSVC assessment: exploitation active17 days later
  5. 13 Aug 2026CVE record last updated1,504 days (about 4 years) later
  6. 12 Nov 2026Analysed by vulneraibility.com91 days (about 3 months) later

CVSS vector

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

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2017-18362 being exploited?

Yes. CVE-2017-18362 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2017-18362?

CVE-2017-18362 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2017-18362?

Not known from our data. No patch reference has been recorded for CVE-2017-18362, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2017-18362 affect?

CVE-2017-18362 affects connectwise:manageditsync. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

4 references in the CVE record, grouped by the tags the record gives them.

Other links (4)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com