log4j 1.2.17 question

[KSD]

We are using the Bamboo server on a closed network.

Recently, I received a call saying that a vulnerability was also found in the 1.2.xx version of log4j.

As a result of checking the Atlassian homepage, it was confirmed that the 1.2.17 version of log4j exists on both the Bamboo server and the Bamboo target server.

I want to know if that jar file is used and if it is vulnerable to security.

Additionally, it would be appreciated if you could tell us the exact config name of log4j used in Bamboo.

I don't see the log4j config file on the target server side.[bamboo-agent]

If there is no config file for log4j , I wonder if it doesn't matter.

thank you.

[Nic Brough -Adaptavist-]

Welcome to the community!

Please see https://community.atlassian.com/t5/Trust-Security-articles/Atlassian-s-Response-to-Log4j-CVE-2021-44228/ba-p/1886598 for the main discussion and pointers to what to do.

[Anik Sengupta]

As explained in the security advisory, Atlassian on-premises products (including Bamboo) use an Atlassian-maintained fork of Log4j 1.2.17, which is not vulnerable to CVE-2021-44228.

We have done additional analysis on this fork and confirmed a new but similar vulnerability that can only be exploited by a trusted party. Please check the security advisory page for details on how you can ensure that you are not vulnerable to this.

For Bamboo Server & Data Center, you will also need to check for remote agents with a custom logging configuration as follows:

If you have a properties file specified for the variable wrapper.java.additional.X=-Dlog4j.configuration (in <bamboo-agent-home>/conf/wrapper.conf), check if the org.apache.log4j.net.JMSAppender is present in the properties file. If it is, you will need to comment it out or remove it.