Atlassian JIRA CVE-2019-15013 Authorization Bypass Vulnerability

Risk

High

Date Discovered

December 16, 2019

Description

Atlassian JIRA is prone to an authorization-bypass vulnerability. An attacker can exploit this issue to bypass certain security restrictions and perform unauthorized actions; this may aid in launching further attacks. The following versions of Atlassian JIRA are affected: Versions prior to 7.13.12 Version 8.0.0 prior to 8.4.3 Version 8.5.0 prior to 8.5.2

Technologies Affected

  • Atlassian JIRA 1.2.1
  • Atlassian JIRA 2.2
  • Atlassian JIRA 2.2.1
  • Atlassian JIRA 2.4.1
  • Atlassian JIRA 2.5.1
  • Atlassian JIRA 2.5.2
  • Atlassian JIRA 2.5.3
  • Atlassian JIRA 2.6
  • Atlassian JIRA 3.0
  • Atlassian JIRA 3.0.2
  • Atlassian JIRA 3.0.3
  • Atlassian JIRA 3.12
  • Atlassian JIRA 3.12.0
  • Atlassian JIRA 3.12.1
  • Atlassian JIRA 3.12.2
  • Atlassian JIRA 3.12.3
  • Atlassian JIRA 3.13
  • Atlassian JIRA 3.13.1
  • Atlassian JIRA 3.13.2
  • Atlassian JIRA 3.13.3
  • Atlassian JIRA 3.13.4
  • Atlassian JIRA 3.13.5
  • Atlassian JIRA 3.2
  • Atlassian JIRA 3.2.1
  • Atlassian JIRA 3.2.2
  • Atlassian JIRA 3.2.3
  • Atlassian JIRA 3.3
  • Atlassian JIRA 3.3.1
  • Atlassian JIRA 3.3.2
  • Atlassian JIRA 3.3.3
  • Atlassian JIRA 3.4.1
  • Atlassian JIRA 3.4.2
  • Atlassian JIRA 3.4.3
  • Atlassian JIRA 3.5.1
  • Atlassian JIRA 3.5.2
  • Atlassian JIRA 3.5.3
  • Atlassian JIRA 3.6
  • Atlassian JIRA 3.6.1
  • Atlassian JIRA 3.6.2
  • Atlassian JIRA 3.6.3
  • Atlassian JIRA 3.6.4
  • Atlassian JIRA 3.6.5
  • Atlassian JIRA 3.7
  • Atlassian JIRA 3.7.1
  • Atlassian JIRA 3.7.2
  • Atlassian JIRA 3.7.3
  • Atlassian JIRA 3.7.4
  • Atlassian JIRA 3.8
  • Atlassian JIRA 3.8.1
  • Atlassian JIRA 3.9
  • Atlassian JIRA 3.9.1
  • Atlassian JIRA 3.9.2
  • Atlassian JIRA 3.9.3
  • Atlassian JIRA 4.0
  • Atlassian JIRA 4.0.1
  • Atlassian JIRA 4.0.2
  • Atlassian JIRA 4.1
  • Atlassian JIRA 4.1.1
  • Atlassian JIRA 4.1.2
  • Atlassian JIRA 4.2
  • Atlassian JIRA 4.2.1
  • Atlassian JIRA 4.2.2
  • Atlassian JIRA 4.2.4
  • Atlassian JIRA 4.3
  • Atlassian JIRA 4.3.3
  • Atlassian JIRA 4.3.4
  • Atlassian JIRA 4.4
  • Atlassian JIRA 4.4.5
  • Atlassian JIRA 5.0
  • Atlassian JIRA 5.0.1
  • Atlassian JIRA 5.0.6
  • Atlassian JIRA 5.1.0
  • Atlassian JIRA 5.1.1
  • Atlassian JIRA 5.1.4
  • Atlassian JIRA 5.1.5
  • Atlassian JIRA 6.0
  • Atlassian JIRA 6.0.1
  • Atlassian JIRA 6.0.2
  • Atlassian JIRA 6.0.3
  • Atlassian JIRA 6.0.4
  • Atlassian JIRA 6.0.5
  • Atlassian JIRA 6.0.7
  • Atlassian JIRA 6.1.3
  • Atlassian JIRA 6.1.4
  • Atlassian JIRA 6.2.1
  • Atlassian JIRA 6.2.5
  • Atlassian JIRA 6.2.7
  • Atlassian JIRA 6.3
  • Atlassian JIRA 6.3.5
  • Atlassian JIRA 6.4.11
  • Atlassian JIRA 6.4.8
  • Atlassian JIRA 7.0.11
  • Atlassian JIRA 7.0.3
  • Atlassian JIRA 7.0.4
  • Atlassian JIRA 7.1.0
  • Atlassian JIRA 7.1.1
  • Atlassian JIRA 7.1.10
  • Atlassian JIRA 7.1.2
  • Atlassian JIRA 7.1.4
  • Atlassian JIRA 7.1.5
  • Atlassian JIRA 7.1.6
  • Atlassian JIRA 7.1.7
  • Atlassian JIRA 7.1.8
  • Atlassian JIRA 7.1.9
  • Atlassian JIRA 7.10.0
  • Atlassian JIRA 7.10.1
  • Atlassian JIRA 7.10.2
  • Atlassian JIRA 7.10.3
  • Atlassian JIRA 7.11.0
  • Atlassian JIRA 7.11.1
  • Atlassian JIRA 7.11.2
  • Atlassian JIRA 7.11.3
  • Atlassian JIRA 7.12.0
  • Atlassian JIRA 7.12.2
  • Atlassian JIRA 7.12.3
  • Atlassian JIRA 7.12.4
  • Atlassian JIRA 7.13.0
  • Atlassian JIRA 7.13.1
  • Atlassian JIRA 7.13.11
  • Atlassian JIRA 7.13.2
  • Atlassian JIRA 7.13.3
  • Atlassian JIRA 7.13.4
  • Atlassian JIRA 7.13.5
  • Atlassian JIRA 7.13.6
  • Atlassian JIRA 7.13.7
  • Atlassian JIRA 7.13.8
  • Atlassian JIRA 7.2.0
  • Atlassian JIRA 7.2.1
  • Atlassian JIRA 7.2.12
  • Atlassian JIRA 7.2.2
  • Atlassian JIRA 7.3.0
  • Atlassian JIRA 7.4.0
  • Atlassian JIRA 7.4.2
  • Atlassian JIRA 7.4.4
  • Atlassian JIRA 7.5.0
  • Atlassian JIRA 7.5.3
  • Atlassian JIRA 7.6.0
  • Atlassian JIRA 7.6.1
  • Atlassian JIRA 7.6.10
  • Atlassian JIRA 7.6.11
  • Atlassian JIRA 7.6.14
  • Atlassian JIRA 7.6.2
  • Atlassian JIRA 7.6.3
  • Atlassian JIRA 7.6.5
  • Atlassian JIRA 7.6.6
  • Atlassian JIRA 7.6.7
  • Atlassian JIRA 7.6.8
  • Atlassian JIRA 7.6.9
  • Atlassian JIRA 7.7.0
  • Atlassian JIRA 7.7.3
  • Atlassian JIRA 7.7.4
  • Atlassian JIRA 7.7.5
  • Atlassian JIRA 7.8.0
  • Atlassian JIRA 7.8.1
  • Atlassian JIRA 7.8.2
  • Atlassian JIRA 7.8.3
  • Atlassian JIRA 7.8.4
  • Atlassian JIRA 7.8.5
  • Atlassian JIRA 7.9.0
  • Atlassian JIRA 7.9.1
  • Atlassian JIRA 7.9.2
  • Atlassian JIRA 7.9.3
  • Atlassian JIRA 8.0.0
  • Atlassian JIRA 8.0.2
  • Atlassian JIRA 8.0.3
  • Atlassian JIRA 8.0.4
  • Atlassian JIRA 8.1.0
  • Atlassian JIRA 8.1.1
  • Atlassian JIRA 8.1.2
  • Atlassian JIRA 8.2.0
  • Atlassian JIRA 8.2.1
  • Atlassian JIRA 8.2.2
  • Atlassian JIRA 8.2.3
  • Atlassian JIRA 8.3.0
  • Atlassian JIRA 8.3.1
  • Atlassian JIRA 8.3.2
  • Atlassian JIRA 8.3.3
  • Atlassian JIRA 8.3.4
  • Atlassian JIRA 8.4.0
  • Atlassian JIRA 8.4.1
  • Atlassian JIRA 8.4.2
  • Atlassian JIRA 8.5.0
  • Atlassian JIRA 8.5.1

Recommendations

Block external access at the network boundary, unless external parties require service.
Use access controls to regulate external access to all services that are not intended to be publicly available.

Run all software as a nonprivileged user with minimal access rights.
To reduce the impact of latent vulnerabilities, always run nonadministrative software as an unprivileged user with minimal access rights.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of suspicious or anomalous activity. This may help detect malicious actions that an attacker may take after successfully exploiting vulnerabilities in applications. Review all applicable logs regularly.

Updates are available. Please see the references or vendor advisory for more information.

References

Credits

SecurityB


© 1995- Symantec Corporation

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com.

Disclaimer

The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.

Symantec, Symantec products, Symantec Security Response, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.