ConnectWise: ScreenConnect attacks continue, update to 26.6.5
ConnectWise says ScreenConnect attacks continue against unpatched on-premises servers. Check for version 26.6.5 or later and review enabled extensions.
TL;DR: ConnectWise says attacks on ScreenConnect continue, and it asks customers to run technician client version 26.6.5 or later. Check your version and the extensions enabled on any on-premises server.
What happened
The Hacker News reported that ConnectWise has finished its investigation into unauthorized access to partner ScreenConnect environments. It advises customers to make sure the technician client is on version 26.6.5 or later. ConnectWise also says activity against on-premises installs is still being reported, where certain third-party extensions remain switched on and systems are unpatched. The toolkit named in the headline is SCKit, which we described in an earlier post.
The new part is the status: this is no longer only a one-off wave, and the vendor is still seeing attempts against servers that have not been updated.
Am I affected?
You are most exposed if you host ScreenConnect yourself, or if a provider uses it to reach your machines. A short review:
- Open the ScreenConnect admin console and read the installed version. Compare it with 26.6.5.
- List the extensions enabled on the server and remove any you do not recognise or no longer need, following ConnectWise's guidance.
- Ask any provider that supports you whether they have done the same.
How to check with Stackurity
Stackurity does not claim to detect ScreenConnect, so the version check above is done by hand. It can still help around the edges: it inventories the Linux servers, images and applications you run and matches them against advisories every hour, and it checks again after a fix to record that the problem is gone. See the verification documentation for how a fix is confirmed.
Start a free trial of Stackurity to keep one live inventory of what you run.