Cross-site request forgery in Atlassian Jira Server
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Tampering
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-352.
Summary
Various installation setup resources in Jira before version 8.5.2 allow remote attackers to configure a Jira instance, which has not yet finished being installed, via Cross-site request forgery (CSRF) vulnerabilities.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
- Fix · CNA Jira Server (Atlassian) Fixed in 8.5.2
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Atlassian Jira Server 8.5.2
2 records Highest priority Priority LOW 2 LOW
Other records, highest priority first
- TI-2019-14634 Uncontrolled search path in Atlassian Jira ServerPriority LOW 34
Timeline
- 2026-10-02 Threatist record created from CVE-2019-20401
- 2026-10-03 Alias added: GHSA-9pj6-pcqj-h4qx
References
More Atlassian Jira Server vulnerabilities
- TI-2019-08654 Injection in Atlassian Jira Server and Data Center KEVCVSS 3.1CRITICAL 9.8
- TI-2022-00460 Improper authentication in Atlassian Jira Core Server CVSS 3.1CRITICAL 9.8
- TI-2024-14399 Code injection in Atlassian Confluence Data Center CVSS 3.1HIGH 8.8
- TI-2021-08038 Path traversal in Atlassian Jira Server KEVCVSS 3.1MEDIUM 5.3
- TI-2020-18587 Incorrect authorization in Atlassian Jira Server CVSS 3.1MEDIUM 5.3
- TI-2019-06067 Server-side request forgery in Atlassian Jira CVSS 3.1MEDIUM 6.5
Sources
- CVE-2019-20401 · CVE Program
- CVE-2019-20401 · NVD
- FIRST EPSS
- GHSA-9pj6-pcqj-h4qx · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences