What is the severity of CVE-2019-8446?

CVE-2019-8446 is considered a medium severity vulnerability due to its potential for username enumeration.

How do I fix CVE-2019-8446?

To fix CVE-2019-8446, upgrade to Jira Server version 8.3.2 or later.

Who is affected by CVE-2019-8446?

CVE-2019-8446 affects all Jira Server versions from 7.6 up to, but not including, 8.3.2.

What type of attack does CVE-2019-8446 enable?

CVE-2019-8446 enables remote attackers to enumerate usernames through an authentication bypass.

Is CVE-2019-8446 a local or remote vulnerability?

CVE-2019-8446 is a remote vulnerability, allowing attackers to exploit it from a remote location.

Vulnerability/
CVE-2019-8446

medium

5.3

CWE

863

23/8/2019

17/9/2024

CVE-2019-8446

First published: Fri Aug 23 2019(Updated: )

The /rest/issueNav/1/issueTable resource in Jira before version 8.3.2 allows remote attackers to enumerate usernames via an incorrect authorisation check.

Credit: security@atlassian.com

Affected Software	Affected Version	How to fix
Atlassian Jira Server	>=7.6<8.3.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-8446?
CVE-2019-8446 is considered a medium severity vulnerability due to its potential for username enumeration.
How do I fix CVE-2019-8446?
To fix CVE-2019-8446, upgrade to Jira Server version 8.3.2 or later.
Who is affected by CVE-2019-8446?
CVE-2019-8446 affects all Jira Server versions from 7.6 up to, but not including, 8.3.2.
What type of attack does CVE-2019-8446 enable?
CVE-2019-8446 enables remote attackers to enumerate usernames through an authentication bypass.
Is CVE-2019-8446 a local or remote vulnerability?
CVE-2019-8446 is a remote vulnerability, allowing attackers to exploit it from a remote location.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
agent/author
agent/weakness
agent/severity
agent/description
agent/tags
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
vendor/atlassian
canonical/atlassian jira server
version/atlassian jira server/7.6

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2019-8446?
CVE-2019-8446 is considered a medium severity vulnerability due to its potential for username enumeration.
How do I fix CVE-2019-8446?
To fix CVE-2019-8446, upgrade to Jira Server version 8.3.2 or later.
Who is affected by CVE-2019-8446?
CVE-2019-8446 affects all Jira Server versions from 7.6 up to, but not including, 8.3.2.
What type of attack does CVE-2019-8446 enable?
CVE-2019-8446 enables remote attackers to enumerate usernames through an authentication bypass.
Is CVE-2019-8446 a local or remote vulnerability?
CVE-2019-8446 is a remote vulnerability, allowing attackers to exploit it from a remote location.