nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Atlassian JIRA Common Credentials - Critical vulnerability

john morrissey

Tenable released a new plugin on 3/22/2019 https://www.tenable.com/plugins/nessus/123003 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?

Comments

Elliot Reiter_zg1zk0

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.

john morrissey

@Elliot Reiter

I'm reaching out to tenable as their tenable.io 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.

https://community.tenable.com/s/feed/0D5f2000067R6nRCAS

john morrissey

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

security