Kaseya Patches VSA Vulnerabilities Used In REvil Ransomware Attack
Kaseya had implemented patches for most of the vulnerabilities on their VSA SaaS service but had not completed the patches for the on-premise version of VSA.
It is unclear which vulnerabilities were used in the attack, but it is believed to be one or a combination of CVE-2021-30116, CVE-2021-30119, and CVE-2021-30120, Bleepingcomputer reports.
Almost ten days after the attacks, Kaseya has released the VSA 9.5.7a (18.104.22.16894) update to fix the vulnerabilities used in the REvil ransomware attack.
With this release, Kaseya has fixed the following vulnerabilities:
- Credentials leak and business logic flaw: CVE-2021-30116
- Cross Site Scripting vulnerability: CVE-2021-30119
- 2FA bypass: CVE-2021-30120
- Fixed an issue where secure flag was not being used for User Portal session cookies.
- Fixed an issue where certain API responses would contain a password hash, potentially exposing any weak passwords to brute force attack. The password value is now masked completely.
- Fixed a vulnerability that could allow unauthorized upload of files to the VSA server.
However, Kaseya is urging customers to follow the ‘On Premises VSA Startup Readiness Guide‘ steps before installing the update to prevent further breaches and make sure devices are not already compromised.
Below are the basic steps that admins should perform before starting up VSA servers again and connecting them to the Internet:
- Ensure your VSA server is isolated
- Check System for Indicators of Compromise (IOC)
- Patch the Operating Systems of the VSA Servers
- Using URL Rewrite to control access to VSA through IIS
- Install FireEye Agent
- Remove Pending Scripts/Jobs
Of these steps, it is critical that on-premise VSA servers not be publicly accessible from the Internet to prevent compromise while installing the patch.
Kaseya also urges customers to utilize their “Compromise Detection Tool,” a collection of PowerShell scripts to detect whether a VSA server or endpoints have been compromised.
The scripts will check VSA servers for the presence of ‘Kaseya\webpages\managedfiles\vsaticketfiles\agent.crt’ and ‘Kaseya\webpages\managedfiles\vsaticketfiles\agent.exe,’ and ‘agent.crt’ and ‘agent.exe’ on endpoints.
The REvil affiliate used the agent.crt and agent.exe files to deploy the REvil ransomware executable.
For additional security, Kaseya is also suggesting on-premise VSA admin restrict access to the web GUI to local IP addresses and those known to be used by security products.
“For VSA On-Premises installations, we have recommended limiting access to the VSA Web GUI to local IP addresses by blocking port 443 inbound on your internet firewall. Some integrations may require inbound access to your VSA server on port 443. Below are a list of IP addresses you can whitelist in your firewall (allow 443 inbound to FROM ), if you are using these integrations with your VSA On-Premises product.” explains Kaseya.
After installing the patch, all users will be required to change their password to one using new password requirements.