CVE-2023-23127
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 · uneditedIn Connectwise Control 22.8.10013.8329, the login page does not implement HSTS headers therefore not enforcing HTTPS. NOTE: 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 confidenceThe Connectwise Control login page does not implement HSTS (HTTP Strict Transport Security) headers, meaning browsers do not receive instruction to remember to only access the site via HTTPS. This allows potential man-in-the-middle attacks where an attacker could intercept the initial HTTP connection and perform session hijacking or credential theft.
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= 22.8.10013.8329CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Connectwise Control installationLocate the Connectwise Control installation directory or check running services on the server. Common paths include C:\Program Files\ConnectWise\Control or /usr/local/connectwise-control/Affected if Connectwise Control software is not installed on the system
-
Determine installed versionCheck the version of Connectwise Control by reviewing the software's about page, release notes, or checking version information in the installation directory. The exact version is 22.8.10013.8329.Affected if The installed version exactly matches 22.8.10013.8329
-
Test for HSTS header presenceSend an HTTPS request to the Connectwise Control login page (typically port 443 or configured HTTPS port) and inspect the response headers. Look for the 'Strict-Transport-Security' header in the server response.Affected if The Strict-Transport-Security header is absent from HTTPS responses
-
Verify HTTP redirect behaviorSend an HTTP request (port 80) to the Connectwise Control server and observe whether it redirects to HTTPS or serves content over plain HTTP.Affected if The server accepts plain HTTP connections without enforcing HTTPS or does not redirect to HTTPS
A system is affected if it runs Connectwise Control version 22.8.10013.8329 and the server responses lack Strict-Transport-Security headers.
Generated from the published advisory. Verify against your own configuration.
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 dataEnable HSTS headers in the Connectwise Control configuration settings, or configure the server to only accept HTTPS connections to enforce secure transport.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23127 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-23127 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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