# CVE-2023-23127: Security feature bypass in n/a

> Missing HSTS headers allow HTTP usage, potentially enabling man-in-the-middle attacks if HTTPS is not enforced by configuration.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Feb 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-6fr7-2fr2-7jh9

## What is CVE-2023-23127?

CVE-2023-23127 is a medium-severity vulnerability in n/a, published on 1 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In 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.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

## Which versions are affected by CVE-2023-23127?

It affects 1 product.


Products: Connectwise Connectwise.

## How do I fix CVE-2023-23127?

No fix has been published for CVE-2023-23127 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-23127 being exploited?

There is no known exploitation of CVE-2023-23127 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-23128](https://insights.sbomify.com/CVE-2023-23128/): Other in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-23127 and fix it if it is affected.

What it is: CVE-2023-23127 is a medium-severity vulnerability in n/a, published on 1 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-23127 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-23127/ (Markdown: https://insights.sbomify.com/CVE-2023-23127/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-23127
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-23127
- OSV: https://osv.dev/vulnerability/CVE-2023-23127

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-23127/
Summaries are generated and may contain mistakes; the official description above is the record.