# CVE-2019-8449: Information disclosure in Jira

> Remote attackers can enumerate usernames via an information disclosure vulnerability in the Jira groupuserpicker resource.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 17 Sep 2024
- **Also known as:** GHSA-8wr9-r69x-g268

## What is CVE-2019-8449?

CVE-2019-8449 is a medium-severity vulnerability in Atlassian Jira, 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 /rest/api/latest/groupuserpicker resource in Jira before version 8.4.0 allows remote attackers to enumerate usernames via an information disclosure vulnerability.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Atlassian Jira.

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

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

## Is CVE-2019-8449 being exploited?

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

Public exploit code:

- CVE-2019-8449 Exploit for Jira v2.1 - v8.3.4 (github_poc): https://github.com/mufeedvh/CVE-2019-8449
- User Enumeration Proof Of Concept Exploit for CVE-2019-8449 (github_poc): https://github.com/r0lh/CVE-2019-8449
- Jira 8.3.4 - Information Disclosure (Username Enumeration) (exploitdb)
- Jira <8.4.0 - Information Disclosure (nuclei): http/cves/2019/CVE-2019-8449.yaml

## 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-2019-8449 and fix it if it is affected.

What it is: CVE-2019-8449 is a medium-severity vulnerability in Atlassian Jira, 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-8449 exists.

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-2019-8449/ (Markdown: https://insights.sbomify.com/CVE-2019-8449/index.md)
```

## Sources

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

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