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 exploit in XRay-Jenkins Plugin

Hello team.

How exposed is the plugin and does it need to be patched?   Our team disabled it to prevent problems over the weekend, but would be great to know if we can re-enable it.




2 answers

1 accepted

0 votes
Answer accepted
Rogério Paiva - Xray Xporter
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Dec 17, 2021

Hi @Christopher Quon and @Jeff Smith 

The Jenkins plugin has been updated to remove the vulnerability and those updates are now available as follows:
  • Xray for JIRA Jenkins Plugin
    Available on the Jenkins Plugin Manager

 Please check the full information here.

Thank you.

Kind regards,
Rogerio Paiva [Xray Support Team]

Hi Rogerio,

I appreciate the response and letting us know about the update. However, it has come to our attention that there are also log4j vulnerabilities with version 2.16 and that 2.17 is now available. Have you investigated whether or not the plugin needs another log4j update?



Hi again Rogerio,

I just found my answer here:

The new plugin (2.5.3) was released a few hours ago.

Thanks again,


We are also interested in knowing when this will be patched.


Jeff Smith

Systems/QA Engineer 

MedImpact Inc

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events