CVE-2019-14995
First published: Wed Sep 11 2019(Updated: )
The /rest/api/1.0/render resource in Jira before version 8.4.0 allows remote anonymous attackers to determine if an attachment with a specific name exists and if an issue key is valid via a missing permissions check.
Credit: security@atlassian.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Jira Server | >=7.6.0<8.4.0 |
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-14995?
CVE-2019-14995 is classified as a medium severity vulnerability.
How do I fix CVE-2019-14995?
To fix CVE-2019-14995, upgrade Jira to version 8.4.0 or later.
Who is affected by CVE-2019-14995?
CVE-2019-14995 affects Atlassian Jira Server versions prior to 8.4.0.
What type of attack can CVE-2019-14995 facilitate?
CVE-2019-14995 can allow remote anonymous attackers to check for the existence of specific attachments.
Is CVE-2019-14995 related to permission checks in Jira?
Yes, CVE-2019-14995 involves a missing permissions check that allows unauthorized access to certain information.
- collector/nvd-index
- agent/weakness
- agent/type
- agent/softwarecombine
- agent/severity
- agent/references
- agent/author
- 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.6.0