Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


Atlassian JIRA Common Credentials - Critical vulnerability


Tenable released a new plugin on 3/22/2019 which while scanning a 7.6.1 jira server installation it flags it as vulnerable.  

The plugin says it's logging in a the default jira/jira uname/pw combo.

Our installation doesn't have that user defined as we change all default settings during initial configuration. 

In grepping the jira security log it never shows the jira user logging in so I think it may be a false positive.

Is anyone else running into seeing this issue?




John, we experienced the exact same vulnerability message yesterday from Nessus with the jira/jira credentials.  This username is clearly not defined among our users.  We think it may very well be a false positive.  We are at Jira v7.11.2.  Thank you for pointing it out.

@Elliot Reiter 

I'm reaching out to tenable as their scanner doesn't report it so I think it's a problem with the nessus pluging.  We went as far as creating a user name jira with a very complex password which didn't help.

I'll update you when I hear back from them.

Ok seems they updated this plugin on the 29th and now it's not falsely reporting the vulnerability so all is good now.



Log in or Sign up to comment