First published: Fri Jan 18 2019(Updated: )
The VerifyPopServerConnection resource in Atlassian Jira before version 7.6.10, from version 7.7.0 before version 7.7.5, from version 7.8.0 before version 7.8.5, from version 7.9.0 before version 7.9.3, from version 7.10.0 before version 7.10.3, from version 7.11.0 before version 7.11.3, from version 7.12.0 before version 7.12.3, and from version 7.13.0 before version 7.13.1 allows remote attackers who have administrator rights to determine the existence of internal hosts & open ports and in some cases obtain service information from internal network resources via a Server Side Request Forgery (SSRF) vulnerability.
Credit: security@atlassian.com
Affected Software | Affected Version | How to fix |
---|---|---|
Atlassian Jira | <7.6.10 | |
Atlassian Server | >=7.7.0<7.7.5 | |
Atlassian Server | >=7.8.0<=7.8.4 | |
Atlassian Server | >=7.9.0<=7.9.2 | |
Atlassian Server | >=7.10.0<=7.10.2 | |
Atlassian Server | >=7.11.0<7.11.3 | |
Atlassian Server | >=7.12.0<7.12.3 | |
Atlassian Server | >=7.13.0<7.13.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2018-13404 is classified as high, indicating a significant risk to affected systems.
To fix CVE-2018-13404, upgrade Atlassian Jira to version 7.6.10 or later for Jira Software or to a patched version as specified.
CVE-2018-13404 affects Atlassian Jira versions up to 7.6.10 and between certain versions in the 7.x series.
CVE-2018-13404 can allow unauthorized access to sensitive information and potentially compromise user accounts.
Yes, Jira Server instances running versions before the patched releases are vulnerable to CVE-2018-13404.