Atlassian JIRA up to 7.13.0 VerifyPopServerConnection server-side request forgery

Summaryinfo

A vulnerability was found in Atlassian JIRA up to 7.13.0. It has been rated as critical. This impacts an unknown function of the component VerifyPopServerConnection. The manipulation leads to server-side request forgery. This vulnerability is referenced as CVE-2018-13404. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Atlassian JIRA up to 7.13.0 (Bug Tracking Software) and classified as critical. This issue affects an unknown function of the component VerifyPopServerConnection. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The bug was discovered 01/18/2019. The weakness was published 02/13/2019. The identification of this vulnerability is CVE-2018-13404 since 07/06/2018. The attack may be initiated remotely. The successful exploitation requires a simple authentication. Neither technical details nor an exploit are publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 26 days. During that time the estimated underground price was around $0-$5k.

Upgrading to version 7.6.10, 7.7.5, 7.8.5, 7.9.3, 7.10.3, 7.11.3, 7.12.3 or 7.13.1 eliminates this vulnerability.

Similar entry is available at VDB-130864. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Bug Tracking Software

Vendor

• Atlassian

Name

• JIRA

Version

• 7.0
• 7.1
• 7.2
• 7.3
• 7.4
• 7.5
• 7.6
• 7.6.0
• 7.6.1
• 7.6.2
• 7.6.3
• 7.6.4
• 7.6.5
• 7.6.6
• 7.6.7
• 7.6.8
• 7.6.9
• 7.7
• 7.7.0
• 7.7.1
• 7.7.2
• 7.7.3
• 7.7.4
• 7.8
• 7.8.0
• 7.8.1
• 7.8.2
• 7.8.3
• 7.8.4
• 7.9
• 7.9.0
• 7.9.1
• 7.9.2
• 7.10
• 7.10.0
• 7.10.1
• 7.10.2
• 7.11
• 7.11.0
• 7.11.1
• 7.11.2
• 7.12
• 7.12.0
• 7.12.1
• 7.12.2
• 7.13.0

License

• commercial

Website

• Vendor: https://www.atlassian.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion