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
4,293,371
Community Members
 
Community Events
165
Community Groups

Is the CVE-2020-14179 issue still present?

Hello,

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.

Here;
https://confluence.atlassian.com/jira/security-advisories-112853939.html

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.
Here:
https://jira.atlassian.com/browse/JRASERVER-71536

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

Here: https://community.atlassian.com/t5/Jira-Core-Server-questions/Sensitive-data-exposure-via-secure-QueryComponent-Default-jspa/qaq-p/1666258

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 Hi, I would like your help and guidance.

Robert Wen Community Leader May 30, 2022

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 https://www.atlassian.com/trust/security/vulnerability-information-report.

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

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

165 views 0 4
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you