# CVE-2018-13404: Server-side request forgery in Jira

> Administrators can exploit an SSRF vulnerability in Jira to scan internal networks and access internal service information.

- **Severity:** Medium 4.1 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5pg5-2rp3-4hw8

## What is CVE-2018-13404?

CVE-2018-13404 is a medium-severity server-side request forgery vulnerability in Atlassian Jira, published on 13 Feb 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2018-13404?

It affects 2 products.


Products: Atlassian Jira, Atlassian Jira Server.

## How do I fix CVE-2018-13404?

No fix has been published for CVE-2018-13404 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-13404 being exploited?

There is no known exploitation of CVE-2018-13404 in the wild and no public exploit code.

## Other vulnerabilities in Atlassian Jira

- [CVE-2020-14172](https://insights.sbomify.com/CVE-2020-14172/): Deserialization in Jira Server (critical 9.8)
- [CVE-2019-20409](https://insights.sbomify.com/CVE-2019-20409/): Code injection in Jira Server (critical 9.8)
- [CVE-2017-5983](https://insights.sbomify.com/CVE-2017-5983/): Deserialization in n/a (critical 9.8)
- [CVE-2010-1165](https://insights.sbomify.com/CVE-2010-1165/): Code injection in n/a (critical 9.0)
- [CVE-2016-4319](https://insights.sbomify.com/CVE-2016-4319/): Cross-site request forgery in Atlassian JIRA Server before 7.1.9 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-13404 and fix it if it is affected.

What it is: CVE-2018-13404 is a medium-severity server-side request forgery vulnerability in Atlassian Jira, published on 13 Feb 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-13404 in the wild and no public exploit code.

Affected product: Atlassian Jira. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-13404/ (Markdown: https://insights.sbomify.com/CVE-2018-13404/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-13404
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-13404
- OSV: https://osv.dev/vulnerability/CVE-2018-13404

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-13404/
Summaries are generated and may contain mistakes; the official description above is the record.