What is CVE-2024-1709?

CVE-2024-1709 is Authentication bypass using an alternate path or channel. The supplied enrichment data classifies it as Auth Bypass mapped to CWE-288 Authentication Bypass Using an Alternate Path.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

107 public PoC repositories reported; 2 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, identity provider logs, authentication audit logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2024-1709 using CVSS 10, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: Kimsuky (), WIZARD SPIDER (), ELECTRUM (), Turla Group (), UNC5174 (), Ransomware use: Known. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVRansomwarecriticalAuth Bypasspublic exploit

CVE-2024-1709

CVE-2024-1709 — Authentication bypass using an alternate path or channel

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2024-1709 in CISA KEV with required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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.

Published Feb 21, 2024Updated Jun 17, 2026Sources: NVD, ConnectWise (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Feb 22, 2024

EPSS

100%

top of FIRST's scoreset

Affects

ConnectWise

ScreenConnect

CVSS base

critical

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade ScreenConnect to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Federal deadline Feb 29, 2024 — passed 928 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
ConnectWise	ScreenConnect	0 to <= 23.9.7	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Changed

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
10	CVSS 3.1	critical	3.9	6	CNA, NVD, ConnectWise (CNA)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-288 · Authentication Bypass Using an Alternate Path or Channel

Bypass Protection Mechanism::

Mitigation: Funnel all access through a single choke point to simplify how users can access a resource. For every access, perform a check to determine if the user has permissions to access the resource.::

Weakness & attack patterns

CWE-288Authentication Bypass Using an Alternate Path

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-127 · Directory Indexing

T1083File and Directory Discovery
T1211Exploitation for Defensive Evasion
T1542.002Pre-OS Boot: Component Firmware

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Feb 22, 2024

Federal deadline

Feb 29, 2024

passed 928 days ago

Ransomware use

Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

2 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Malware

Families a CTI source ties to this CVE. One named, with the total it tracks.

Families tracked

Named

blackbasta

win.blackbasta, elf.blackbasta, Black Basta

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

12 more posts on this CVEShowing 5 of 17 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable ScreenConnect.
Monitor for scanner or exploit-pattern traffic after 107 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSidentity provider logsauthentication audit logs

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

KimsukyWIZARD SPIDERELECTRUMTurla GroupUNC5174

33 more threat groups on this CVEShowing 5 of 38 · Attribution, campaigns and the malware each one runsUnlock free

hostnamehadujaza.com82
Cyber Threat Alliance (CTA) · Sep 19, 2022
ip45.77.159.25246
Cyber Threat Alliance (CTA) · Sep 26, 2022
ip70.49.33.20058
Cyber Threat Alliance (CTA) · Sep 16, 2022
ip70.51.132.19758
usom.phishing-General-List · Sep 13, 2022
ip89.211.217.3870
Cyber Threat Alliance (CTA) · Sep 20, 2022

5 more indicators on this CVEShowing 5 of 10 · Hashes, addresses and domains from a live threat exchangeUnlock free

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 10.0 (AV:N)
Jun 17, 2026 · NVD
Cve is exploited tdawg506/ScreenConnect-CVE-2024-1709-Exploit
May 4, 2026 · SOCRadar CTI
2024
Added to CISA KEV catalog
Feb 22, 2024 · CISA
Initial · CVE published
Feb 21, 2024 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

20×SVRS was changedApr 30, 2026 – Jun 8, 2026 · SOCRadar CTI
11×TweetsMar 20, 2026 – Aug 19, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Jun 2, 2026 · SOCRadar CTI

References

12 on the record

github.com/rapid7/metasploit-framework/pull/18870
Issue Tracking, Patch, Third Party Advisory, NIST, GITHUB
github.com/watchtowrlabs/connectwise-screenconnect_auth-bypass-add-user-poc
Exploit, Third Party Advisory, GITHUB, NIST
techcrunch.com/2024/02/21/researchers-warn-high-risk-connectwise-flaw-under-attack-is-embarrassingly-easy-to-exploit/
Press/Media Coverage, Third Party Advisory, GITHUB, NIST
www.bleepingcomputer.com/news/security/connectwise-urges-screenconnect-admins-to-patch-critical-rce-flaw/
Press/Media Coverage, Third Party Advisory, NIST, GITHUB
www.connectwise.com/company/trust/security-bulletins/connectwise-screenconnect-23.9.8
Vendor Advisory, NIST
www.horizon3.ai/attack-research/red-team/connectwise-screenconnect-auth-bypass-deep-dive/
Third Party Advisory, GITHUB, NIST
www.huntress.com/blog/a-catastrophe-for-control-understanding-the-screenconnect-authentication-bypass
Exploit, Third Party Advisory, GITHUB, NIST
www.huntress.com/blog/detection-guidance-for-connectwise-cwe-288-2
Exploit, Third Party Advisory, GITHUB, NIST

Coverage

16 stories from the feeds we poll

11 more reports on this CVEShowing 5 of 16 · Vendor research and security press coverageUnlock free

Elsewhere on this site

ConnectWiseevery CVE for this vendor
February 2024what else CISA listed
Auth Bypasssame class
CWE-288other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 5 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2024-1709 is Authentication bypass using an alternate path or channel, a critical vulnerability affecting ScreenConnect from ConnectWise. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 107 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 10 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.