Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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,461,688
Community Members
 
Community Events
176
Community Groups

Authentication bypass in Jira (CVE 2022 0540) vulnerability if JIRA is internal on the network only

Regarding the recently announced critical security advisory for CVE-2022-0540 regarding Authentication bypass in JIRA Server, is this still a critical vulnerability if the JIRA instance is confined to the internal network only and is not accessible from the internet?

2 answers

1 accepted

0 votes
Answer accepted

That's a question only you and your org's security team (if you have one) can answer for sure. If you trust everyone with access to your internal network, then it may not be so critical for you because only people on your internal network would be able to exploit it.

0 votes
Filipi Lima Atlassian Team Apr 21, 2022

Hi Robert,

On the FAQ, we have added an answer to that question as well:

My instance isn't exposed to the Internet. Is an upgrade still recommended?

Yes! While ensuring instances are not exposed to the public internet greatly reduces the attack surface, we always recommend upgrading when security fixes are available. We try to provide as much information as possible so that customers can determine the scope (e.g. affected products, and in this case, affected apps) and impact. It's ultimately up to each customer to consider this information when determining whether mitigating factors, like no external access to the instance, reduces the risk to their business enough to defer installing an upgrade.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events