dbcve.org
AutomateApplication · Connectwise

CVE-2023-47257

HIGH · 8.1 CVSS v3.1 Published 2024-02-01
Fix available
A fix is available. Upgrade to 23.8.5 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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
ConnectWise ScreenConnect through 23.8.4 allows man-in-the-middle attackers to achieve remote code execution via crafted messages.

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 · moderate confidence

ConnectWise ScreenConnect through 23.8.4 contains a man-in-the-middle vulnerability where an attacker positioned on the network can intercept and modify communications between client and server, allowing injection of crafted messages that lead to remote code execution on the affected system.

MitigationUpgrade ScreenConnect to version 23.9.7 or later. As a temporary mitigation, ensure ScreenConnect traffic traverses only trusted networks or VPN tunnels to reduce MITM attack surface.

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
AutomateApplication
Affected:all versions
ScreenconnectApplication
Affected:< 23.8.5

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

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

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

  1. Identify installed ConnectWise products
    Check for ScreenConnect or Automate installation: Review installed programs list, check for ScreenConnect or Automate services in Windows Services, or search for installation directories (typically in C:\Program Files\ScreenConnect or C:\Program Files\Automate)
    Affected if Either ScreenConnect or ConnectWise Automate is present on the system
  2. Determine ScreenConnect version
    If ScreenConnect is installed, locate the version: Check the ScreenConnect installation directory for version info, or query the ScreenConnect service via its web interface (usually port 8040 or 443), or check the Windows installed programs list for the exact version number
    Affected if ScreenConnect version is lower than 23.8.5 (any version < 23.8.5 is affected)
  3. Check Automate installation status
    Verify if ConnectWise Automate is installed: Look in Windows Services for 'Automate' or 'LabTech' service, check installed programs, or search for Automate installation paths
    Affected if ConnectWise Automate is installed (all versions are affected per the CVE)
  4. Assess network exposure for MITM risk
    Evaluate whether the ScreenConnect or Automate web interfaces (ports 8040, 443, 80, 4433) are accessible from untrusted networks: Review firewall rules allowing external access, check router/NAT configurations exposing these services to the internet, and verify VPN status for remote access
    Affected if The management interface is accessible from untrusted/public networks without VPN tunneling, creating MITM attack surface

You are affected if ConnectWise ScreenConnect version < 23.8.5 OR any version of ConnectWise Automate is installed AND the management interface is reachable from untrusted networks where a man-in-the-middle attack is possible.

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.

dbcve · scoped
Upgrade available Upgrade to 23.8.5 or later
Fixed in 23.8.5
Interim mitigation

Upgrade ScreenConnect to version 23.9.7 or later. As a temporary mitigation, ensure ScreenConnect traffic traverses only trusted networks or VPN tunnels to reduce MITM attack surface.

Recommended fix Moderate confidence

ScreenConnect 23.8.5 or later

  1. 1. Back up your current ScreenConnect installation and database before proceeding
  2. 2. Download ScreenConnect version 23.8.5 or later from the official ConnectWise portal
  3. 3. Review the release notes for version 23.8.5 for any specific installation instructions
  4. 4. Apply the upgrade following ConnectWise standard upgrade procedures
  5. 5. Verify the upgrade was successful by checking the ScreenConnect control panel
  6. 6. Confirm the version number reflects 23.8.5 or higher
Caveat Check release notes for any configuration or compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Automate Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47257 — 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-2023-47257 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