log4j & cloud Confluence?

[Timo Hilbertz]

hi, since the official statement about log4j is pretty brief (not to say lame), i'm looking for answers here. The vulnerability has been disclosed 4 days ago and still Confluence does not give any update. Anyone here who can help? Is the Confluence Data Center Cloud version vulnerable or not?

[Daniel Eads · Accepted solution]

Hi all,

Daniel with Atlassian Support here to let you know our security team has finished its investigation. We have an official response statement here on Community, which you can access at this link.

More information can be found on our advisory page, as well as the previously-published FAQ:

• https://confluence.atlassian.com/display/SECURITY/Multiple+Products+Security+Advisory+-+Log4j+Vulnerable+To+Remote+Code+Execution+-+CVE-2021-44228
• https://confluence.atlassian.com/kb/faq-for-cve-2021-44228-1103069406.html

Thanks,
Daniel Eads | Atlassian Support

[Timo Hilbertz]

sorry, my bad: i mixed up the Confluence terminologies. I mean the Confluence Cloud version, not the Data Center version.

[David Rodman]

I checked our log4j version and it was 1.x  Since the vulnerability is in 2.x we are not affected.

[colin mcdermott]

Yes this is true. 

Yet what this means is that Atlassian needs to upgrade to log4j version2.16 ASAP. 

Version 1 is 2015. 

I.e. https://www.cvedetails.com/cve/CVE-2019-17571/

Also check if the org.apache.log4j.JMSAppender module is enabled, as per the articles posted by others. Then you are still vulnerable even with version 1(should not apply to cloud instances, only server/DC). 

[Alfredo Negrete]

It depends on the version you have and version of the Log4j files you're using...check this site: 

https://confluence.atlassian.com/kb/faq-for-cve-2021-44228-1103069406.html