What is the severity of CVE-2019-8448?

CVE-2019-8448 has a medium severity rating due to its potential for information disclosure.

How do I fix CVE-2019-8448?

To fix CVE-2019-8448, upgrade to Jira Server version 7.13.4 or 8.2.2 or later.

What does CVE-2019-8448 exploit?

CVE-2019-8448 exploits an information disclosure vulnerability allowing attackers to enumerate usernames.

Which versions of Jira are affected by CVE-2019-8448?

Versions of Jira before 7.13.4 and between 8.0.0 and 8.2.2 are affected by CVE-2019-8448.

Can CVE-2019-8448 lead to further attacks?

Yes, CVE-2019-8448 can lead to further attacks by allowing attackers to gather valid usernames.

Vulnerability/
CVE-2019-8448

medium

5.3

13/8/2019

16/9/2024

CVE-2019-8448

First published: Tue Aug 13 2019(Updated: )

The login.jsp resource in Jira before version 7.13.4, and from version 8.0.0 before version 8.2.2 allows remote attackers to enumerate usernames via an information disclosure vulnerability.

Credit: security@atlassian.com

Affected Software	Affected Version	How to fix
Atlassian Jira Server	>=7.11.0<7.13.4
Atlassian Jira Server	>=8.0.0<8.2.2

Never miss a vulnerability like this again

Reference Links

https://jira.atlassian.com/browse/JRASERVER-69797

Frequently Asked Questions

What is the severity of CVE-2019-8448?
CVE-2019-8448 has a medium severity rating due to its potential for information disclosure.
How do I fix CVE-2019-8448?
To fix CVE-2019-8448, upgrade to Jira Server version 7.13.4 or 8.2.2 or later.
What does CVE-2019-8448 exploit?
CVE-2019-8448 exploits an information disclosure vulnerability allowing attackers to enumerate usernames.
Which versions of Jira are affected by CVE-2019-8448?
Versions of Jira before 7.13.4 and between 8.0.0 and 8.2.2 are affected by CVE-2019-8448.
Can CVE-2019-8448 lead to further attacks?
Yes, CVE-2019-8448 can lead to further attacks by allowing attackers to gather valid usernames.

collector/nvd-index
agent/type
agent/softwarecombine
agent/author
agent/references
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.11.0
version/atlassian jira server/8.0.0

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-8448?
CVE-2019-8448 has a medium severity rating due to its potential for information disclosure.
How do I fix CVE-2019-8448?
To fix CVE-2019-8448, upgrade to Jira Server version 7.13.4 or 8.2.2 or later.
What does CVE-2019-8448 exploit?
CVE-2019-8448 exploits an information disclosure vulnerability allowing attackers to enumerate usernames.
Which versions of Jira are affected by CVE-2019-8448?
Versions of Jira before 7.13.4 and between 8.0.0 and 8.2.2 are affected by CVE-2019-8448.
Can CVE-2019-8448 lead to further attacks?
Yes, CVE-2019-8448 can lead to further attacks by allowing attackers to gather valid usernames.