# CVE-2024-1709: ConnectWise ScreenConnect Authentication Bypass

> Attackers can bypass authentication to access confidential information and critical systems in ConnectWise ScreenConnect.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 22 Feb 2024 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2024
- **Updated:** 21 Oct 2025
- **Also known as:** CVE-2024-27215, GHSA-cg3j-75xh-7fv3

## What is CVE-2024-1709?

CVE-2024-1709 is a critical authentication bypass vulnerability in ConnectWise ScreenConnect, published on 21 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ConnectWise ScreenConnect 23.9.7 and prior are affected by an Authentication Bypass Using an Alternate Path or Channel

 vulnerability, which may allow an attacker direct access to confidential information or 

critical systems.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2024-1709?

It affects 1 product.


Products: Connectwise Screenconnect.

## How do I fix CVE-2024-1709?

No fix has been published for CVE-2024-1709 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 29 Feb 2024.

## Is CVE-2024-1709 being exploited?

Yes. Attackers have exploited CVE-2024-1709 in the wild since at least 22 Feb 2024, including in ransomware campaigns.

Public exploit code:

- ScreenConnect AuthBypass(cve-2024-1709) --> RCE!!! (github_poc): https://github.com/W01fh4cker/ScreenConnect-AuthBypass-RCE
- A Scanner for CVE-2024-1709 - ConnectWise SecureConnect Authentication Bypass Vulnerability (github_poc): https://github.com/HussainFathy/CVE-2024-1709
- https://github.com/sxyrxyy/CVE-2024-1709-ConnectWise-ScreenConnect-Authentication-Bypass (github_poc): https://github.com/sxyrxyy/CVE-2024-1709-ConnectWise-ScreenConnect-Authentication-Bypass
- https://github.com/cjybao/CVE-2024-1709-and-CVE-2024-1708 (github_poc): https://github.com/cjybao/CVE-2024-1709-and-CVE-2024-1708
- ConnectWise ScreenConnect Unauthenticated Remote Code Execution (metasploit)
- Event ID 229 Rule Name SOC262 ScreenConnect Authentication Bypass Exploitation Detected (CVE-2024-1709) (github_poc): https://github.com/AhmedMansour93/Event-ID-229-Rule-Name-SOC262-CVE-2024-1709-

## Other vulnerabilities in ConnectWise ScreenConnect

- [CVE-2026-84869](https://insights.sbomify.com/CVE-2026-84869/): ConnectWise ScreenConnect Improper Privilege Management and Missing Authorization (critical 9.9, exploited in the wild)
- [CVE-2024-1708](https://insights.sbomify.com/CVE-2024-1708/): ConnectWise ScreenConnect Path Traversal (high 8.4, exploited in the wild)
- [CVE-2025-3935](https://insights.sbomify.com/CVE-2025-3935/): ConnectWise ScreenConnect Improper Authentication (high 8.1, exploited in the wild)
- [CVE-2025-14265](https://insights.sbomify.com/CVE-2025-14265/): Improper server-side validation in ScreenConnect extension framework (critical 9.1)
- [CVE-2025-14823](https://insights.sbomify.com/CVE-2025-14823/): Certificate Signing Extension Returns Encrypted Values (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1709 and fix it if it is affected.

What it is: CVE-2024-1709 is a critical authentication bypass vulnerability in ConnectWise ScreenConnect, published on 21 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-1709 in the wild since at least 22 Feb 2024, including in ransomware campaigns.

Affected product: ConnectWise ScreenConnect. 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-2024-1709/ (Markdown: https://insights.sbomify.com/CVE-2024-1709/index.md)
```

## Sources

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

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