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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Is Jira server vulnerable to CVE-2021-44228

I'm keeping an eye on this question. Is there any information about the potential impact of CVE-2021-44228 on Jira Core Server versions?


3 answers

2 accepted

Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 13, 2021 • edited

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.

Additionally there is more information available on our advisory page, as well as the previously-published FAQ:

Daniel Eads | Atlassian Support

0 votes
Answer accepted
Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 10, 2021

Hi all,

Daniel from Atlassian Support here. I'd just like to provide you with this preliminary FAQ related to the log4j zero-day. Our Security team is currently investigating the impact of the Log4j remote code execution vulnerability (CVE-2021-44228) and determining any possible impacts. In the meantime, hopefully this FAQ will help address some initial questions you may have.

Daniel Eads | Atlassian Support

0 votes
Clark Everson
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 10, 2021 • edited

Hi @James 

Welcome to the Community! I would keep an eye on that post but honestly once Atlassian recognizes it they will send out an email usually to the billing account person on your account if your instance is vulnerable. They will also post with the vulnerability and the affected versions.

There's already a few posts about this and it would be really hard for them to respond to each individually.



Roger that, Thanks!

A possibility is to add "-Dlog4j2.formatMsgNoLookups=true" to the JVM startup parameters in which I am guessing Atlassian will eventually tell us to do...


Edit: this property only applies to log4j version 2.10 to 2.14 so would not help as jira/confluence use an older version. Refer to the Atlassian FAQ posted by Daniel.

There is a jar (\Atlassian\JIRA\atlassian-jira\WEB-INF\lib\log4j2-stacktrace-origins-2.2-atlassian-2.jar) that apparently refers to the version 2.x

Like Mohan Sundar likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events