JIRA up to 8.3.1 issueTable Username improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in JIRA up to 8.3.1. It has been rated as problematic. The impacted element is an unknown function of the file /rest/issueNav/1/issueTable. Performing a manipulation results in improper authorization (Username). This vulnerability was named CVE-2019-8446. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in JIRA up to 8.3.1. This affects an unknown function of the file /rest/issueNav/1/issueTable. The manipulation with an unknown input leads to a improper authorization vulnerability (Username). CWE is classifying the issue as 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. This is going to have an impact on confidentiality. The summary by CVE is:
The /rest/issueNav/1/issueTable resource in Jira before version 8.3.2 allows remote attackers to enumerate usernames via an incorrect authorisation check.
The weakness was presented 08/23/2019. This vulnerability is uniquely identified as CVE-2019-8446 since 02/18/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. 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 8.3.2 eliminates this vulnerability.
See VDB-140764, VDB-140762 and VDB-140761 for similar entries. Statistical analysis made it clear that VulDB provides the best quality 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 8.3.2
Timeline
02/18/2019 🔍08/23/2019 🔍
08/24/2019 🔍
12/01/2023 🔍
Sources
Advisory: jira.atlassian.comStatus: Not defined
CVE: CVE-2019-8446 (🔍)
GCVE (CVE): GCVE-0-2019-8446
GCVE (VulDB): GCVE-100-140763
See also: 🔍
Entry
Created: 08/24/2019 12:18Updated: 12/01/2023 18:00
Changes: 08/24/2019 12:18 (38), 08/04/2020 20:07 (17), 12/01/2023 18:00 (4)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.