JIRA up to 8.3.x groupuserpicker Username information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in JIRA up to 8.3.x and classified as problematic. The affected element is an unknown function of the file /rest/api/latest/groupuserpicker. This manipulation causes information disclosure (Username). This vulnerability is tracked as CVE-2019-8449. The attack is possible to be carried out remotely. Moreover, an exploit is present. The affected component should be upgraded.
Details
A vulnerability classified as problematic was found in JIRA up to 8.3.x. Affected by this vulnerability is an unknown part of the file /rest/api/latest/groupuserpicker. The manipulation with an unknown input leads to a information disclosure vulnerability (Username). The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
The /rest/api/latest/groupuserpicker resource in Jira before version 8.4.0 allows remote attackers to enumerate usernames via an information disclosure vulnerability.
The weakness was disclosed 09/11/2019 (Website). The advisory is shared at jira.atlassian.com. This vulnerability is known as CVE-2019-8449 since 02/18/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1592 for this issue.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
Upgrading to version 8.4.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Exploit-DB (47990). The entries VDB-141699 and VDB-141698 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: UsernameClass: Information disclosure / Username
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: JIRA 8.4.0
Timeline
02/18/2019 🔍09/11/2019 🔍
09/12/2019 🔍
12/02/2024 🔍
Sources
Advisory: 156172Status: Confirmed
Confirmation: 🔍
CVE: CVE-2019-8449 (🔍)
GCVE (CVE): GCVE-0-2019-8449
GCVE (VulDB): GCVE-100-141697
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 09/12/2019 08:45Updated: 12/02/2024 01:36
Changes: 09/12/2019 08:45 (57), 08/21/2020 11:44 (1), 12/19/2023 14:39 (4), 12/02/2024 01:36 (25)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.