What is the severity of CVE-2019-8445?

CVE-2019-8445 is classified as a high severity vulnerability due to its potential for remote exploitation.

How do I fix CVE-2019-8445?

To fix CVE-2019-8445, upgrade to Jira version 7.13.7 or version 8.3.2 or later.

What does CVE-2019-8445 affect?

CVE-2019-8445 affects Atlassian Jira Server versions prior to 7.13.7 and versions from 8.0.0 to 8.3.2.

What type of attack does CVE-2019-8445 allow?

CVE-2019-8445 allows attackers to view worklog time information by bypassing permissions checks.

Is CVE-2019-8445 due to a configuration issue?

No, CVE-2019-8445 is due to a missing permissions check in the Jira application code.

Vulnerability/
CVE-2019-8445

medium

5.3

CWE

862 863

23/8/2019

17/9/2024

CVE-2019-8445

First published: Fri Aug 23 2019(Updated: )

Several worklog rest resources in Jira before version 7.13.7, and from version 8.0.0 before version 8.3.2 allow remote attackers to view worklog time information via a missing permissions check.

Credit: security@atlassian.com

Affected Software	Affected Version	How to fix
Atlassian Jira Server	>=7.13.0<7.13.7
Atlassian Jira Server	>=8.0.0<8.3.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-8445?
CVE-2019-8445 is classified as a high severity vulnerability due to its potential for remote exploitation.
How do I fix CVE-2019-8445?
To fix CVE-2019-8445, upgrade to Jira version 7.13.7 or version 8.3.2 or later.
What does CVE-2019-8445 affect?
CVE-2019-8445 affects Atlassian Jira Server versions prior to 7.13.7 and versions from 8.0.0 to 8.3.2.
What type of attack does CVE-2019-8445 allow?
CVE-2019-8445 allows attackers to view worklog time information by bypassing permissions checks.
Is CVE-2019-8445 due to a configuration issue?
No, CVE-2019-8445 is due to a missing permissions check in the Jira application code.

collector/nvd-index
agent/references
agent/weakness
agent/type
agent/softwarecombine
agent/author
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.13.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-8445?
CVE-2019-8445 is classified as a high severity vulnerability due to its potential for remote exploitation.
How do I fix CVE-2019-8445?
To fix CVE-2019-8445, upgrade to Jira version 7.13.7 or version 8.3.2 or later.
What does CVE-2019-8445 affect?
CVE-2019-8445 affects Atlassian Jira Server versions prior to 7.13.7 and versions from 8.0.0 to 8.3.2.
What type of attack does CVE-2019-8445 allow?
CVE-2019-8445 allows attackers to view worklog time information by bypassing permissions checks.
Is CVE-2019-8445 due to a configuration issue?
No, CVE-2019-8445 is due to a missing permissions check in the Jira application code.