dbcve.org
AutomateApplication · Connectwise

CVE-2023-47256

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-01
Fix available
A fix is available. Upgrade to 23.8.5 or later.
See remediation →
57/100
Remediation priority · Elevated
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 local users to connect to arbitrary relay servers via implicit trust of proxy settings

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 version 23.8.4 improperly trusts proxy settings, allowing local users to redirect the application's connections to arbitrary relay servers instead of legitimate ones. This could enable a local attacker to perform man-in-the-middle attacks or intercept/redirect ScreenConnect traffic.

MitigationUpgrade ScreenConnect to the latest patched version. Until then, restrict local user access to system configuration and monitor for unauthorized proxy configuration changes.

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

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

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 ScreenConnect installation and version
    Check the installed version of ConnectWise ScreenConnect. On Windows, look in Add/Remove Programs or check the installation directory for version information. Compare the version number to the affected range (< 23.8.5).
    Affected if ScreenConnect version is 23.8.4 or earlier, or the version cannot be determined but is < 23.8.5
  2. Locate proxy configuration files or settings
    Search for proxy configuration files related to ScreenConnect. Check the ScreenConnect installation directory and Windows system proxy settings that the application may be using. Look for config files with 'proxy' in the name or containing proxy-related settings.
    Affected if Proxy configuration files or settings exist for the ScreenConnect application
  3. Verify who can modify proxy settings
    Review file system permissions on the proxy configuration files or registry keys. Check if standard users have write access to proxy settings that ScreenConnect uses. Use Windows permissions tools (icacls) or review ACLs on relevant config files.
    Affected if Non-privileged users have write access to proxy configuration used by ScreenConnect
  4. Inspect current proxy configuration values
    Examine the current proxy settings for ScreenConnect. Check for unexpected or suspicious proxy server addresses, particularly localhost (127.0.0.1) or unfamiliar IP addresses that could indicate a relay server configured by an attacker.
    Affected if Proxy settings point to unexpected hosts, localhost ports, or unfamiliar relay servers not authorized by the organization
  5. Review Windows proxy settings inheritance
    Check if ScreenConnect is configured to respect system or user-level proxy settings. Look for configuration options that determine whether the application trusts proxy settings from the operating system or user environment.
    Affected if ScreenConnect is configured to trust proxy settings from the system or user environment without admin approval

A system is affected if ScreenConnect version is less than 23.8.5 AND proxy settings can be modified by local users or point to unauthorized relay servers.

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 the latest patched version. Until then, restrict local user access to system configuration and monitor for unauthorized proxy configuration changes.

Recommended fix High confidence

ScreenConnect 23.8.5 or later

  1. 1. Upgrade ScreenConnect to version 23.8.5 or later to remediate the improper authentication vulnerability

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

Fix this in Automate Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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