Login Request a demo
Medium severity · published Jun 29, 2020
CVE-2019-20412
The Convert Sub-Task to Issue page in affected versions of Atlassian Jira Server and Data Center allow remote attackers to enumerate the following information via an Improper…
5.3
CVSS
1.9%
EPSS
No
On KEV
Description
The Convert Sub-Task to Issue page in affected versions of Atlassian Jira Server and Data Center allow remote attackers to enumerate the following information via an Improper Authentication vulnerability: Workflow names; Project Key, if it is part of the workflow name; Issue Keys; Issue Types; Status Types. The affected versions are before version 7.13.9, and from version 8.0.0 before 8.4.2.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
Low
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)1.9% · higher than 79% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
JI
Jira · Atlassian
before 7.13.9 · source: NVD
JD
Jira Data Center · Atlassian
8.0.0 before 8.4.2 · source: NVD
JS
Jira Software Data Center · Atlassian
before 7.13.9 · source: NVD
Affected product
JI
Jira
Atlassian
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2019-20412
CVE.org
https://www.cve.org/CVERecord?id=CVE-2019-20412
Vendor Advisory
https://jira.atlassian.com/browse/JRASERVER-70882
More from Jira
9.8
CVE-2019-11581
Atlassian Jira Server and Data Center Server-Side Template Injection Vulnerability
5.3
CVE-2021-26086
Atlassian Jira Server and Data Center Path Traversal Vulnerability
9.8
CVE-2022-26136
A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to bypass Servlet Filters used by first and third party apps
9.8
CVE-2022-0540
A vulnerability in Jira Seraph allows a remote, unauthenticated attacker to bypass authentication by sending a specially crafted HTTP request
9.8
CVE-2020-14172
This issue exists to document that a security improvement in the way that Jira Server and Data Center use velocity templates has been implemented