Security Issue Log4j

[svnc]

Dear Team,

due to the current security vulnerability of log4j we need urgent information to how the jira server is affected.

Thanks in advance

Regards, Sevinc

[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

[svnc]

Thank you Daniel

[Beeraiah Velumula]

@Daniel Eads - Thank you so much!

[jy]

will like to check if there is any intention to upgrade its log4j to 2.17.1?

[jy]

https://stackoverflow.com/questions/70334503/cve-2021-44228-and-log4j-1-2-17

As log4j 1.x does not offer a look-up mechanism, it does not suffer from CVE-2021-44228. However, note that log4j 1.x is no longer being maintained.

[Mohamed Riza _ServiceRocket_ · Accepted solution]

Hi @svnc 

You may check the information provided by Atlassian in the following link: https://confluence.atlassian.com/kb/faq-for-cve-2021-44228-1103069406.html. Basically, only if you have org.apache.log4j.net.JMSAppender in your log4j, you may be vulnerable. The mitigation is to disable this temporarily. 

[svnc]

Thank you Mohamed!