Medium severity · published Feb 12, 2020
CVE-2019-20099
The VerifyPopServerConnection!add.jspa component in Atlassian Jira Server and Data Center before version 8.7.0 is vulnerable to cross-site request forgery (CSRF)
4.3
CVSS
0.7%
EPSS
No
On KEV
Description
The VerifyPopServerConnection!add.jspa component in Atlassian Jira Server and Data Center before version 8.7.0 is vulnerable to cross-site request forgery (CSRF). An attacker could exploit this by tricking an administrative user into making malicious HTTP requests, allowing the attacker to enumerate hosts and open ports on the internal network where Jira server is present.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Confidentiality
Low
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.7% · higher than 55% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
JI
Jira · Atlassian
7.6.15 before 8.5.4; 8.5.5 before 8.6.2 · source: NVD
JD
Jira Data Center · Atlassian
7.6.15 before 8.5.4; 8.5.5 before 8.6.2 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2019-20099
CVE.org
https://www.cve.org/CVERecord?id=CVE-2019-20099
Issue Tracking
https://jira.atlassian.com/browse/JRASERVER-70606
Exploit
https://www.tenable.com/security/research/tra-2020-05
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