# CVE-2019-8451: Server-side request forgery in Jira

> Remote attackers can access internal network resources via SSRF in Jira's makeRequest servlet due to a whitelist logic bug.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hp98-w9mh-2g6q

## What is CVE-2019-8451?

CVE-2019-8451 is a medium-severity server-side request forgery vulnerability in Atlassian Jira Server, published on 11 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The /plugins/servlet/gadgets/makeRequest resource in Jira before version 8.4.0 allows remote attackers to access the content of internal network resources via a Server Side Request Forgery (SSRF) vulnerability due to a logic bug in the JiraWhitelist class.

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

## Which versions are affected by CVE-2019-8451?

It affects 1 product.


Products: Atlassian Jira Server.

## How do I fix CVE-2019-8451?

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

## Is CVE-2019-8451 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-8451 exists.

Public exploit code:

- Jira未授权SSRF漏洞 (github_poc): https://github.com/jas502n/CVE-2019-8451
- https://jira.atlassian.com/browse/JRASERVER-69793 (github_poc): https://github.com/0xbug/CVE-2019-8451
- POC to check for Jira instances vulnerable to CVE-2019-8451 (github_poc): https://github.com/h0ffayyy/Jira-CVE-2019-8451
- https://github.com/ianxtianxt/CVE-2019-8451 (github_poc): https://github.com/ianxtianxt/CVE-2019-8451
- exploit for atlassian jira server SSRF (github_poc): https://github.com/iuds/CVE-2019-8451
- Jira <8.4.0 - Server-Side Request Forgery (nuclei): http/cves/2019/CVE-2019-8451.yaml

## Other vulnerabilities in Atlassian Jira Server

- [CVE-2019-11581](https://insights.sbomify.com/CVE-2019-11581/): Atlassian Jira Server and Data Center Server-Side Template Injection (critical 9.8, exploited in the wild)
- [CVE-2019-20400](https://insights.sbomify.com/CVE-2019-20400/): Code injection in Jira Server (high 7.8)
- [CVE-2020-14177](https://insights.sbomify.com/CVE-2020-14177/): Denial of service in Jira Server (medium 6.5)
- [CVE-2019-20401](https://insights.sbomify.com/CVE-2019-20401/): Cross-site request forgery in Jira Server (medium 6.5)
- [CVE-2019-14998](https://insights.sbomify.com/CVE-2019-14998/): Cross-site request forgery in Jira (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-8451 and fix it if it is affected.

What it is: CVE-2019-8451 is a medium-severity server-side request forgery vulnerability in Atlassian Jira Server, published on 11 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-8451 exists.

Affected product: Atlassian Jira Server. 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-2019-8451/ (Markdown: https://insights.sbomify.com/CVE-2019-8451/index.md)
```

## Sources

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

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