Skip to content
NewA calmer, faster ZeroHour
Exploit / PoCcriticalExploited in the wild

Threat Brief: Atlassian Confluence Remote Code Execution Vulnerability (CVE-2022

Palo Alto Unit 42by Abhishek Anbazhagan, Shawn Westfall, Daniela Shalev, Eli Barr, Josh Grunzweig ()5 min read1 · 1 read
AI summary · glm-5.3-flashSummaries by Vani AI

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.

Key facts
  • 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
Analyze CVE-2022-26134 with Vani AIImpact, affected versions, exploitation, mitigations and detection

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2022-26134
Unauthenticated OGNL Injection RCE in Atlassian Confluence Server/Data Center
9.8100%KEVRansomwarePoC ×2
KEV

Indicators of compromise

auto-extracted · verify before use · export allAll
TypeIndicatorContext
ipv4167.99.57.116Ipv4 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
ipv4172.104.31.117iginated 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
ipv418.216.140.250v4 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
ipv418.221.234.103v4 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
ipv4191.37.248.120llowing 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
ipv4192.99.152.200pv4 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
ipv4193.106.191.71v4 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
ipv42.56.11.6518.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
ipv427.1.1.3487.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
ipv431.13.191.157pv4 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,
ipv484.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
ipv487.249.135.167pv4 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
ipv489.187.170.129193.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.

Palo Alto Unit 42

By Abhishek Anbazhagan, Shawn Westfall, Daniela Shalev, Eli Barr, Josh Grunzweig · unit42.paloaltonetworks.com

Read the full article at Palo Alto Unit 42

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.