Threat Brief: Atlassian Confluence Remote Code Execution Vulnerability (CVE-2022
Unauthenticated Confluence RCE CVE-2022-26134 was exploited in the wild; Volexity observed intrusions and Cerber ransomware on unpatched servers.
Volexity identified exploitation of CVE-2022-26134, an unauthenticated remote code execution vulnerability in Atlassian Confluence Server and Data Center, during Memorial Day weekend 2022, with Atlassian issuing a patch. Cortex Xpanse found 19,707 potentially affected Confluence instances, concentrated in the US, Germany, China, and Russia, plus 1,251 end-of-life versions exposed. Unit 42 and Cortex Managed Threat Hunting observed successful exploitation leading to reconnaissance commands and a Cerber ransomware deployment that was blocked by Cortex XDR. A public PoC has increased exploitation risk.
- CVE-2022-26134 is unauthenticated RCE allowing auth bypass and arbitrary code execution
- Volexity first observed exploitation over Memorial Day weekend 2022
- Xpanse counted 19,707 potentially vulnerable Confluence servers exposed worldwide
- Successful exploitation led to Cerber ransomware, blocked by Cortex XDR
- Public PoC available; Atlassian patch released and immediate patching advised
- CVEs
- CVE-2022-26134
- ATT&CK
- T1190 Exploit Public-Facing ApplicationT1059.001 Command and Scripting Interpreter: PowerShellT1033 Account Discovery: Owner/User DiscoveryT1082 System Information DiscoveryT1486 Data Encrypted for Impact
- Malware
- Cerber
- Organizations
- AtlassianVolexityPalo Alto Networks
- Countries
- United StatesGermanyChinaRussia
Vulnerabilities mentioned
All| CVE | Vulnerability | CVSS | EPSS | Signals | Published |
|---|---|---|---|---|---|
| CVE-2022-26134 | Unauthenticated OGNL Injection RCE in Atlassian Confluence Server/Data Center | 9.8 | 100% | KEVRansomwarePoC ×2 | KEV |
Indicators of compromise
auto-extracted · verify before use · export allAll| Type | Indicator | Context |
|---|---|---|
| ipv4 | 167.99.57.116 | Ipv4 192.99.152.200 Ipv4 31.13.191.157 Ipv4 27.1.1.34 Ipv4 167.99.57.116 (Table updated Sept. 22, 2022, to remove an IP address that |
| ipv4 | 172.104.31.117 | iginated from the following IP addresses: IoC Type IoC Ipv4 172.104.31.117 Ipv4 191.37.248.120 Ipv4 84.17.48.94 Ipv4 193.106.191.71 Ip |
| ipv4 | 18.216.140.250 | v4 191.37.248.120 Ipv4 84.17.48.94 Ipv4 193.106.191.71 Ipv4 18.216.140.250 Ipv4 18.221.234.103 Ipv4 89.187.170.129 Ipv4 2.56.11.65 Ipv |
| ipv4 | 18.221.234.103 | v4 84.17.48.94 Ipv4 193.106.191.71 Ipv4 18.216.140.250 Ipv4 18.221.234.103 Ipv4 89.187.170.129 Ipv4 2.56.11.65 Ipv4 87.249.135.167 Ipv |
| ipv4 | 191.37.248.120 | llowing IP addresses: IoC Type IoC Ipv4 172.104.31.117 Ipv4 191.37.248.120 Ipv4 84.17.48.94 Ipv4 193.106.191.71 Ipv4 18.216.140.250 Ip |
| ipv4 | 192.99.152.200 | pv4 89.187.170.129 Ipv4 2.56.11.65 Ipv4 87.249.135.167 Ipv4 192.99.152.200 Ipv4 31.13.191.157 Ipv4 27.1.1.34 Ipv4 167.99.57.116 (Table |
| ipv4 | 193.106.191.71 | v4 172.104.31.117 Ipv4 191.37.248.120 Ipv4 84.17.48.94 Ipv4 193.106.191.71 Ipv4 18.216.140.250 Ipv4 18.221.234.103 Ipv4 89.187.170.129 |
| ipv4 | 2.56.11.65 | 18.216.140.250 Ipv4 18.221.234.103 Ipv4 89.187.170.129 Ipv4 2.56.11.65 Ipv4 87.249.135.167 Ipv4 192.99.152.200 Ipv4 31.13.191.157 |
| ipv4 | 27.1.1.34 | 87.249.135.167 Ipv4 192.99.152.200 Ipv4 31.13.191.157 Ipv4 27.1.1.34 Ipv4 167.99.57.116 (Table updated Sept. 22, 2022, to remove |
| ipv4 | 31.13.191.157 | pv4 2.56.11.65 Ipv4 87.249.135.167 Ipv4 192.99.152.200 Ipv4 31.13.191.157 Ipv4 27.1.1.34 Ipv4 167.99.57.116 (Table updated Sept. 22, |
| ipv4 | 84.17.48.94 | : IoC Type IoC Ipv4 172.104.31.117 Ipv4 191.37.248.120 Ipv4 84.17.48.94 Ipv4 193.106.191.71 Ipv4 18.216.140.250 Ipv4 18.221.234.103 |
| ipv4 | 87.249.135.167 | pv4 18.221.234.103 Ipv4 89.187.170.129 Ipv4 2.56.11.65 Ipv4 87.249.135.167 Ipv4 192.99.152.200 Ipv4 31.13.191.157 Ipv4 27.1.1.34 Ipv4 |
| ipv4 | 89.187.170.129 | 193.106.191.71 Ipv4 18.216.140.250 Ipv4 18.221.234.103 Ipv4 89.187.170.129 Ipv4 2.56.11.65 Ipv4 87.249.135.167 Ipv4 192.99.152.200 Ipv |
From the original article
5 min read at unit42.paloaltonetworks.com
On June 2, Volexity reported that over Memorial Day weekend, they identified suspicious activity on two internet-facing servers running Atlassian’s Confluence Server application. After analysis of the compromise, Volexity determined the initial foothold was the result of a remote code execution vulnerability in Confluence Server and Data Center.
By Abhishek Anbazhagan, Shawn Westfall, Daniela Shalev, Eli Barr, Josh Grunzweig · unit42.paloaltonetworks.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.