Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,349
Community Members
 
Community Events
176
Community Groups

log4j & cloud Confluence?

Edited

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?

4 answers

1 accepted

1 vote
Answer accepted

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:

Thanks,
Daniel Eads | Atlassian Support

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

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

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). 

Like David Rodman likes this

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

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events