Active exploitation of ScreenConnect CVE-2024-1709 persists as week opens, putting MSP customer fleets at risk
Marcus Webb ·
Threat actors are still abusing ConnectWise ScreenConnect CVE-2024-1709 to gain administrator access to remote support servers and push payloads into managed service provider environments as teams return on Monday. Incidents continue to involve rapid lateral movement into customer networks, data theft, and ransomware deployment, according to incident response firms tracking active cases.
This matters because a single exposed ScreenConnect instance can serve dozens or hundreds of downstream tenants. Exploitation remains attractive to ransomware affiliates due to direct administrative reach and the ability to bypass endpoint controls from a trusted tool.
Exploitation and impact
CVE-2024-1709 is an authentication bypass that allows unauthenticated access to administrative functions on vulnerable ScreenConnect servers. Attackers also chain CVE-2024-1708 for path traversal to plant web shells and persistence. Both flaws were added to CISA’s Known Exploited Vulnerabilities catalog in 2024 and continue to show a long tail of unpatched systems.
Observed post exploitation activity includes creation of rogue ScreenConnect administrator users, abuse of the built in command feature to run PowerShell, deployment of Cobalt Strike or Sliver, disablement of security agents, and use of PsExec for lateral movement. Data exfiltration via Rclone or cloud storage often precedes ransomware such as Black Basta or LockBit delivered to multiple tenants in a single operation.
What defenders should do now
Identify and isolate any ScreenConnect server that is not on 23.9.8 or later. If a vulnerable build was internet exposed, assume compromise, rebuild from a known good image, and rotate all credentials managed through the platform, including downstream local admin accounts and service accounts.
Hunt for new or unexpected ScreenConnect admin users, unknown extensions, and recent use of the remote command feature in audit logs. Review EDR and Windows telemetry for child processes spawned by ScreenConnect services, new scheduled tasks or services with random names, and PsExec executions originating from the ScreenConnect host.
Constrain ScreenConnect management interfaces behind VPN, restrict by source IP, and enforce SSO with phishing resistant MFA. Disable interactive command features for high risk groups, and require just in time elevation. Monitor egress from ScreenConnect servers for cloud storage domains and unusual data volumes. If Microsoft 365 or Google Workspace access originates from the ScreenConnect host, revoke tokens and refresh all OAuth app consents.
For the broader technology landscape, the persistence of exploitation against remote management and edge admin tools underscores that IT operations platforms are Tier 0 assets. Vendors and customers need emergency patch service level objectives, network isolation by default, and continuous inventory to keep these control planes out of reach of affiliates that monetize access at scale.