CVE-2019-3399
First published: Mon Apr 29 2019(Updated: )
The BrowseProjects.jspa resource in Jira before version 7.13.2, and from version 8.0.0 before version 8.0.2 allows remote attackers to see information for archived projects through a missing authorisation check.
Credit: security@atlassian.com security@atlassian.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Jira Core | <7.13.2 | |
| Atlassian Server | >=8.0.0<8.0.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-3399?
CVE-2019-3399 is classified as a medium severity vulnerability.
How do I fix CVE-2019-3399?
To mitigate CVE-2019-3399, upgrade Jira to version 7.13.2 or version 8.0.2 or later.
What does CVE-2019-3399 expose?
CVE-2019-3399 allows remote attackers to see information for archived projects due to a missing authorization check.
Which versions of Jira are affected by CVE-2019-3399?
Versions of Jira before 7.13.2 and from 8.0.0 before 8.0.2 are affected by CVE-2019-3399.
Is CVE-2019-3399 related to Jira Server?
Yes, CVE-2019-3399 also affects Jira Server versions in the specified ranges.
- agent/type
- agent/weakness
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/references
- agent/description
- agent/first-publish-date
- agent/last-modified-date
- agent/author
- agent/softwarecombine
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- vendor/atlassian
- canonical/atlassian jira core
- canonical/atlassian server
- version/atlassian server/8.0.0