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!


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
Community Members
Community Events
Community Groups

log4j 1.2.17 question


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.

2 answers

2 votes
Nic Brough -Adaptavist-
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 16, 2021

Welcome to the community!

Please see for the main discussion and pointers to what to do.

0 votes
Anik Sengupta
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 12, 2022

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 (in <bamboo-agent-home>/conf/wrapper.conf), check if the is present in the properties file. If it is, you will need to comment it out or remove it.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events