dbcve.org
AutomateApplication · Connectwise

CVE-2023-23130

MEDIUM · 5.9 CVSS v3.1 Published 2023-02-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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 Automate 2022.11 is vulnerable to Cleartext authentication. Authentication is being done via HTTP (cleartext) with SSL disabled. OTE: the vendor's position is that, by design, this is controlled by a configuration option in which a customer can choose to use HTTP (rather than HTTPS) during troubleshooting.

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

Connectwise Automate 2022.11 transmits authentication credentials over HTTP in cleartext when SSL is disabled. An attacker on the same network could intercept these credentials through passive traffic monitoring or man-in-the-middle attacks.

MitigationEnable SSL and disable HTTP for authentication in the Connectwise Automate configuration settings. Ensure production environments do not use the troubleshooting HTTP option.

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:= 2022.11

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
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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. Verify Connectwise Automate version
    Check the installed Connectwise Automate version in the system. This can typically be found in the application itself (usually under Help > About or System > Dashboard), or check the installer/logs if recently upgraded.
    Affected if The installed version is exactly 2022.11 (this CVE affects only this specific version)
  2. Confirm SSL is disabled for the web interface
    Access the Connectwise Automate server configuration or registry settings related to SSL/TLS. Check the web server settings within Automate (typically under System > Security or System > Configuration) to verify whether SSL/TLS is enabled or disabled.
    Affected if SSL/TLS is disabled and the web interface is accessible over HTTP instead of HTTPS
  3. Verify HTTP is enabled for authentication
    Check the Automate configuration settings to determine whether HTTP (non-SSL) access is permitted for the login/authentication pages. This is often found in the web server or network settings within Automate.
    Affected if HTTP is enabled and allowed for authentication traffic (credentials transmitted over port 80 instead of 443)
  4. Inspect network listener for HTTP port
    On the Connectwise Automate server, use netstat or similar tool to verify if the server is listening on HTTP port 80 (and not just HTTPS port 443). This confirms the service is accessible over unencrypted HTTP.
    Affected if The server is listening on port 80 for HTTP authentication traffic

You are affected if you have Connectwise Automate version 2022.11 installed AND SSL is disabled, allowing authentication credentials to be transmitted over unencrypted HTTP.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable SSL and disable HTTP for authentication in the Connectwise Automate configuration settings. Ensure production environments do not use the troubleshooting HTTP option.

Recommended fix Moderate confidence
  1. Ensure SSL/HTTPS is enabled in Connectwise Automate by configuring the server to require HTTPS for all authentication connections
  2. Navigate to the Automate administrative interface and verify that the 'Require SSL' or 'Force HTTPS' option is enabled
  3. If troubleshooting mode was temporarily enabled to use HTTP, disable it after troubleshooting is complete
  4. Verify all authentication traffic is now encrypted by confirming connections use HTTPS (port 443) rather than HTTP (port 80)
  5. Review network logs to confirm no cleartext authentication credentials are being transmitted

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

Fix this in Automate Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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