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

Is the CVE-2020-14179 issue still present?


We are using version 8.20.1 as jira server. However, we received a vulnerability notice today. CVE-2020-14179 we've done the readings for the issue here. I couldn't find such an open number on the Jira security page.


In the aforementioned solution request, there is information that it has not been resolved. In the last comment someone mentioned that it was fixed. However, atlassian has not confirmed this.

On the community page, someone stated that the problem was not resolved on April 16, 2021, it was not working.


It's been a quirky process.

In the last case, can anyone who has knowledge about this issue inform us?
Is version 8.20.1 valid for this threat or not?

3 answers

1 accepted

0 votes
Answer accepted

@Robert Wen_ReleaseTEAM_ Hi, I would like your help and guidance.

Based on what I'm reading, Atlassian "solved" the issue by creating the dark features.  On your version, you should incorporate one of the two fixes:

To workaround this bug on Jira versions listed in "fixed in versions" above, one of the two techniques can be used:

Like serkan_sezer likes this
1 vote
Filipi Lima Atlassian Team May 30, 2022

Hello, @serkan_sezer , I see that we've delivered a fix for this CVE for a while now and we have no confirmation of sensitive information being disclosed through that vector.

One thing that I've see more than a couple times in the past weeks is when clients upgrade their Jira Software but their Jira Server Management is still not updated causing the Vulnerability check to trigger an alert.

If your team was able to reproduce any vulnerability, they can follow the Vulnerability Information steps

@Filipi Lima Hi, I would like your help and guidance.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events