CVE-2019-8449 json
The /rest/api/latest/groupuserpicker resource in Jira before version 8.4.0 allows remote attackers to enumerate usernames via an informatio…
published 7y ago modified 4mo ago also EUVD-2019-17839
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 85.7%
- EPSS 85.7% chance of exploitation in 30 days, percentile 99.7%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
The /rest/api/latest/groupuserpicker resource in Jira before version 8.4.0 allows remote attackers to enumerate usernames via an information disclosure vulnerability.
Patch / fix
- Atlassian Jira 8.4.0
Is CVE-2019-8449 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-47990)
Exploit prediction
85.74% chance of exploitation in the next 30 days, higher than 99.7% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-47990 Jira 8.3.4 - Information Disclosure (Username Enumeration) webapps, 2020-02-03
- Nuclei template Jira <8.4.0 - Information Disclosure nuclei detection template
- packetstormsecurity.com http://packetstormsecurity.com/files/156172/Jira-8.3.4-Information-Disclosure.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- Atlassian Jira
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
References
-
packetstormsecurity.com
/files/156172/Jira-8.3.4-Information-Disclosure.html
exploit, third-party-advisory, vdb-entry
-
jira.atlassian.com
/browse/JRASERVER-69796
issue-tracking, vendor-advisory
Sources
- CVE List CVE-2019-8449
- NVD CVE-2019-8449
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.