What is the severity of CVE-2019-15013?

CVE-2019-15013 is classified as a medium severity vulnerability due to its impact on project status configuration.

How do I fix CVE-2019-15013?

To resolve CVE-2019-15013, upgrade your Jira instance to version 7.13.12 or versions 8.4.3 and 8.5.2 or later.

Who is affected by CVE-2019-15013?

CVE-2019-15013 affects authenticated users without project administration access in Jira versions prior to the specified fixed versions.

What kind of access does an attacker need for CVE-2019-15013?

An attacker needs authenticated access to Jira but does not require project administration access to exploit CVE-2019-15013.

What can attackers do with CVE-2019-15013?

Attackers exploiting CVE-2019-15013 can remove configured issue statuses from Jira projects, potentially disrupting project workflows.

Vulnerability/
CVE-2019-15013

medium

4.3

CWE

862

18/12/2019

5/8/2024

CVE-2019-15013

First published: Wed Dec 18 2019(Updated: )

The WorkflowResource class removeStatus method in Jira before version 7.13.12, from version 8.0.0 before version 8.4.3, and from version 8.5.0 before version 8.5.2 allows authenticated remote attackers who do not have project administration access to remove a configured issue status from a project via a missing authorisation check.

Credit: security@atlassian.com

Affected Software	Affected Version	How to fix
Atlassian JIRA	<7.13.12
Atlassian Jira Server	>=8.0.0<8.4.3
Atlassian Jira Server	>=8.5.0<8.5.2

Never miss a vulnerability like this again

Reference Links

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

Frequently Asked Questions

What is the severity of CVE-2019-15013?
CVE-2019-15013 is classified as a medium severity vulnerability due to its impact on project status configuration.
How do I fix CVE-2019-15013?
To resolve CVE-2019-15013, upgrade your Jira instance to version 7.13.12 or versions 8.4.3 and 8.5.2 or later.
Who is affected by CVE-2019-15013?
CVE-2019-15013 affects authenticated users without project administration access in Jira versions prior to the specified fixed versions.
What kind of access does an attacker need for CVE-2019-15013?
An attacker needs authenticated access to Jira but does not require project administration access to exploit CVE-2019-15013.
What can attackers do with CVE-2019-15013?
Attackers exploiting CVE-2019-15013 can remove configured issue statuses from Jira projects, potentially disrupting project workflows.

collector/nvd-index
agent/type
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/last-modified-date
agent/references
agent/author
agent/description
agent/softwarecombine
agent/first-publish-date
agent/event
agent/tags
agent/source
vendor/atlassian
canonical/atlassian jira
canonical/atlassian jira server
version/atlassian jira server/8.0.0
version/atlassian jira server/8.5.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-15013?
CVE-2019-15013 is classified as a medium severity vulnerability due to its impact on project status configuration.
How do I fix CVE-2019-15013?
To resolve CVE-2019-15013, upgrade your Jira instance to version 7.13.12 or versions 8.4.3 and 8.5.2 or later.
Who is affected by CVE-2019-15013?
CVE-2019-15013 affects authenticated users without project administration access in Jira versions prior to the specified fixed versions.
What kind of access does an attacker need for CVE-2019-15013?
An attacker needs authenticated access to Jira but does not require project administration access to exploit CVE-2019-15013.
What can attackers do with CVE-2019-15013?
Attackers exploiting CVE-2019-15013 can remove configured issue statuses from Jira projects, potentially disrupting project workflows.