We've been busy as a team working through support efforts for instances affected by recent exploits arising from Confluence vulnerabilities published at:
- https://confluence.atlassian.com/doc/confluence-security-advisory-2019-04-17-968660855.html
- https://confluence.atlassian.com/doc/confluence-security-advisory-2019-03-20-966660264.html
There's been some pretty busy community posts arising from these as sys-admin teams work to secure and upgrade affected systems, including:
- https://community.atlassian.com/t5/Confluence-discussions/khugepageds-eating-all-of-the-CPU/td-p/1055337
- https://community.atlassian.com/t5/Confluence-questions/WARNING-Confluence-server-hacked/qaq-p/1054136
- https://community.atlassian.com/t5/Confluence-questions/How-come-my-confluence-installation-was-hacked-by-Kerberods/qaq-p/1054605
One of our team, @Jeff Turner took the time to write a detailed advisory note on the steps you should be taking to secure a compromised system whilst balancing the need to gather evidence of the exploit and minimising service disruption.
In Australia, that means also considering the notification criteria published by the Australian Cyber Security Centre and the threshold for Notifiable Data Breaches scheme, which is a legal obligation locally.
By communicating with Cyber response agencies in your respective country, you're helping to make co-ordinating agencies aware of the issue to minimise damage and shorten the recovery window.
If you're not yet using the Atlassian Incident Management Playbook, now would be a very good time to start.
