JIRA up to 7.13.2/8.0.3/8.1.0 /rest/api/2/user/picker Username improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in JIRA up to 7.13.2/8.0.3/8.1.0. Affected by this issue is some unknown functionality of the file /rest/api/2/user/picker. This manipulation causes improper authorization (Username). This vulnerability is tracked as CVE-2019-3403. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability was found in JIRA up to 7.13.2/8.0.3/8.1.0. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the file /rest/api/2/user/picker. The manipulation with an unknown input leads to a improper authorization vulnerability (Username). The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality. The summary by CVE is:
The /rest/api/2/user/picker rest resource in Jira before version 7.13.3, from version 8.0.0 before version 8.0.4, and from version 8.1.0 before version 8.1.1 allows remote attackers to enumerate usernames via an incorrect authorisation check.
The weakness was disclosed 05/22/2019. This vulnerability is known as CVE-2019-3403 since 12/19/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1548.002 according to MITRE ATT&CK.
Upgrading to version 7.13.3, 8.0.4 or 8.1.1 eliminates this vulnerability.
The entries VDB-135366 and VDB-135365 are pretty similar. Be aware that VulDB is the high quality source for 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.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Improper authorization / Username
CWE: CWE-285 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: JIRA 7.13.3/8.0.4/8.1.1
Timeline
12/19/2018 🔍05/22/2019 🔍
05/23/2019 🔍
09/23/2023 🔍
Sources
Advisory: jira.atlassian.comStatus: Not defined
CVE: CVE-2019-3403 (🔍)
GCVE (CVE): GCVE-0-2019-3403
GCVE (VulDB): GCVE-100-135367
See also: 🔍
Entry
Created: 05/23/2019 12:19Updated: 09/23/2023 16:17
Changes: 05/23/2019 12:19 (39), 06/14/2020 16:40 (17), 09/23/2023 16:17 (4)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.