CVE-2024-1708: ConnectWise ScreenConnect Path Traversal Vulnerability
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
ConnectWise ScreenConnect 23.9.7 and prior are affected by path-traversal vulnerability, which may allow an attacker the ability to execute remote code or directly impact confidential data or critical systems.
Description quoted from the CVE record (assigned by cisa-cg, published 2024-02-21).
Weakness: CWE-22 Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)
How it can be exploited
Exploitable over the network with low attack complexity needing high privileges and a user must take an action. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.
- On CISA KEV since
- 2026-04-28
- US federal deadline
- 2026-05-12
- Ransomware use
- Yes
Public exploit evidence (Exploit Observer)
Also known as: BDU:2024-01532, CNNVD-202402-1751, EUVD-2024-17442, GHSA-65x5-26gm-j9pq
VEDAS cluster: VEDAS:BELLCRACKLE
Exploit Observer links 8 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (8)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Nuclei template: https://raw.githubusercontent.com/projectdiscovery/nuclei-templates/main/http/cves/2024/CVE-2024-1708.yaml
- Code repository: https://github.com/cjybao/cve-2024-1709-and-cve-2024-1708
- Code repository: https://github.com/razureink/cve-2024-1708-connectwise_rce_reproduction
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/nuclei/2024/CVE-2024-1708.yaml
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/nuclei/2024/CVE-2024-1708.yaml
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2024/CVE-2024-1708.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2024/CVE-2024-1708.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2024/CVE-2024-1708.rules
Research and write-ups (2)
- Research or write-up: https://instatunnel.my/blog/understanding-cve-2024-1709-and-cve-2024-1708---the-authentication-bypass-that-shook-remote-access-security
- Research or write-up: https://www.huntress.com/blog/slashandgrab-screen-connect-post-exploitation-in-the-wild-cve-2024-1709-cve-2024-1708
Vulnerability databases and vendor advisories (6)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2024-17442
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-65x5-26gm-j9pq
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2024-1708
- Vulnerability database or vendor advisory: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-1708
- Vulnerability database or vendor advisory: https://www.cnnvd.org.cn/home/globalSearch?keyword=CNNVD-202402-1751
- Vulnerability database or vendor advisory: https://www.tenable.com/cve/CVE-2024-1708
696 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.954
very likely to be attacked soon - VEDAS
- 0.989
strong exploit evidence - On CISA KEV
- Yes, since 2026-04-28
Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.
VEDAS flagged this bug about 254 days before CISA confirmed attacks.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| ConnectWise ScreenConnect | up to and including 23.9.7 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
Exploit Observer also maps it to: connectwise screenconnect, connectwise,_llc. connectwise_screenconnect.
How to fix it
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor guidance:
- https://www.connectwise.com/company/trust/security-bulletins/connectwise-screenconnect-23.9.8
- https://nvd.nist.gov/vuln/detail/CVE-2024-1708
How to detect it
Nuclei template (active check)
ConnectWise ScreenConnect - Path Traversal
ConnectWise ScreenConnect 23.9.7 and prior are affected by path-traversal vulnerability, which may allow an attacker the ability to execute remote code or directly impact confidential data or critical systems.
Name and description quoted from the template, written by VEDAS.
The template sends 1 request (GET /); it decides using dsl, regex matchers. Severity in the template: high. Marked as not yet verified against a live vulnerable target.
Run it against a host you own or are authorised to test:
nuclei -u https://your-host -t CVE-2024-1708.yamlShow the template (47 lines)
id: CVE-2024-1708
info:
name: "ConnectWise ScreenConnect - Path Traversal"
author: vedas-arpsyndicate
severity: high
description: |
ConnectWise ScreenConnect 23.9.7 and prior are affected by path-traversal vulnerability, which may allow an
attacker the ability to execute remote code or directly impact confidential data or critical systems.
reference:
- https://www.exploit.observer/?keyword=CVE-2024-1708&match=exact
- https://subdomain.center/?engine=ammonites&keyword=connectwise&match=exact
classification:
cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
cvss-score: 8.4
cve-id: CVE-2024-1708
cwe-id: CWE-22
metadata:
verified: false
tags: cve,cve2024,connectwise,screenconnect,lfi,kev,vkev
http:
- raw:
- |
GET / HTTP/1.1
Host: {{Hostname}}
matchers:
- type: dsl
dsl:
- contains(header, "ScreenConnect/")
- compare_versions(version, '<= 23.9.7')
condition: and
extractors:
- type: regex
name: version
part: header
group: 1
regex:
- 'ScreenConnect/([0-9]+\.[0-9]+\.[0-9]+)'
internal: true
- type: regex
part: header
group: 1
regex:
- 'ScreenConnect/([0-9]+\.[0-9]+\.[0-9]+)'
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2024-1708 ConnectWise ScreenConnect - Path Traversal. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2024-1708 ConnectWise ScreenConnect - Path Traversal"; flow:established,to_client; file.data; content:"ScreenConnect/"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2024-1708; reference:url,https://www.exploit.observer/?keyword=CVE-2024-1708&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=connectwise&match=exact; sid:1011415; rev:1;)
References
Exploits and technical analysis
- https://www.microsoft.com/en-us/security/blog/2026/04/06/storm-1175-focuses-gaze-on-vulnerable-web-facing-assets-in-high-tempo-medusa-ransomware-operations/ (third-party-advisory)
Government sources
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-1708 (government-resource)
Other references
- https://www.connectwise.com/company/trust/security-bulletins/connectwise-screenconnect-23.9.8
- https://www.huntress.com/blog/a-catastrophe-for-control-understanding-the-screenconnect-authentication-bypass
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.