dbcve.org
Automate ApiApplication · Connectwise

CVE-2020-14159

HIGH · 8.8 CVSS v3.1 Published 2020-06-15
Fix available
A fix is available. Upgrade to 2019.12.337 / 2020.1.53 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
By using an Automate API in ConnectWise Automate before 2020.5.178, a remote authenticated user could execute commands and/or modifications within an individual Automate instance by triggering an SQL injection vulnerability in /LabTech/agent.aspx. This affects versions before 2019.12.337, 2020 before 2020.1.53, 2020.2 before 2020.2.85, 2020.3 before 2020.3.114, 2020.4 before 2020.4.143, and 2020.5 before 2020.5.178.

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 confidence

SQL injection vulnerability in the /LabTech/agent.aspx API endpoint of ConnectWise Automate allows authenticated remote users to execute arbitrary SQL commands and potentially modify data within the Automate instance database.

MitigationUpgrade ConnectWise Automate to version 2019.12.337 or later for the 2019 branch, or 2020.1.53/2020.2.85/2020.3.114/2020.4.143/2020.5.178 or later depending on the 2020 release train in use.

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
Automate ApiApplication
Affected:< 2019.12.337>= 2020, < 2020.1.53>= 2020.2, < 2020.2.85>= 2020.3, < 2020.3.114>= 2020.4, < 2020.4.143>= 2020.5, < 2020.5.178

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ConnectWise Automate installation
    Check if the web application is accessible at your Automate server URL. The product was formerly known as LabTech, so look for /LabTech/ or /Automate/ paths in the URL.
    Affected if The /LabTech/agent.aspx endpoint is present and accessible on your server
  2. Locate the installed version number
    Access the Automate web interface and navigate to Help > About, or check the Control Center for the version. The version is also displayed on the login page or in the footer of the web interface.
    Affected if The displayed version number matches one of the affected ranges: < 2019.12.337, >= 2020 but < 2020.1.53, >= 2020.2 but < 2020.2.85, >= 2020.3 but < 2020.3.114, >= 2020.4 but < 2020.4.143, or >= 2020.5 but < 2020.5.178
  3. Verify the agent.aspx API endpoint is exposed
    Attempt to access https://yourserver/LabTech/agent.aspx or https://yourserver/Agent/agent.aspx through a web browser or curl command. Note whether the endpoint returns a response or redirects to login.
    Affected if The endpoint is accessible without immediate authentication error or returns a valid response indicating the API is enabled
  4. Confirm remote access is permitted
    Determine if the web interface allows remote connections. Check if the Automate server is configured to accept external connections for the API endpoint, typically via the web server settings or firewall rules.
    Affected if The server accepts remote HTTP/HTTPS connections to the Automate web port from untrusted networks

Your environment is affected if ConnectWise Automate is running and the /LabTech/agent.aspx endpoint is accessible remotely with a version number matching any of the vulnerable release ranges listed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 2019.12.337 / 2020.1.53 / 2020.2.85 or later
Fixed in 2019.12.3372020.1.532020.2.85
Interim mitigation

Upgrade ConnectWise Automate to version 2019.12.337 or later for the 2019 branch, or 2020.1.53/2020.2.85/2020.3.114/2020.4.143/2020.5.178 or later depending on the 2020 release train in use.

Fix this in Automate Api Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-14159 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-14159 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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