Atlassian JIRA Server/Data Center up to 7.13.11/8.5.3/8.6.0 Access Control Comment default permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in Atlassian JIRA Server and Data Center up to 7.13.11/8.5.3/8.6.0. Affected by this issue is some unknown functionality of the component Access Control. Such manipulation as part of Comment leads to default permission. This vulnerability is traded as CVE-2019-20106. The attack may be launched remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as critical, has been found in Atlassian JIRA Server and Data Center up to 7.13.11/8.5.3/8.6.0 (Bug Tracking Software). Affected by this issue is an unknown function of the component Access Control. The manipulation as part of a Comment leads to a default permission vulnerability. Using CWE to declare the problem leads to CWE-276. During installation, installed file permissions are set to allow anyone to modify those files. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Comment properties in Atlassian Jira Server and Data Center before version 7.13.12, from 8.0.0 before version 8.5.4, and 8.6.0 before version 8.6.1 allows remote attackers to make comments on a ticket to which they do not have commenting permissions via a broken access control bug.
The weakness was shared 02/06/2020. This vulnerability is handled as CVE-2019-20106 since 12/30/2019. The exploitation is known to be easy. The attack may be launched remotely. The successful exploitation requires a simple authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1222.
Upgrading to version 7.13.12, 8.5.4 or 8.6.1 eliminates this vulnerability.
The entries VDB-149748 and VDB-149747 are related to this item. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
- 7.13.0
- 7.13.1
- 7.13.2
- 7.13.3
- 7.13.4
- 7.13.5
- 7.13.6
- 7.13.7
- 7.13.8
- 7.13.9
- 7.13.10
- 7.13.11
- 8.0
- 8.1
- 8.2
- 8.3
- 8.4
- 8.5
- 8.5.0
- 8.5.1
- 8.5.2
- 8.5.3
- 8.6.0
License
Website
- Vendor: https://www.atlassian.com/
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: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.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
Class: Default permissionCWE: CWE-276 / 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 Server/Data Center 7.13.12/8.5.4/8.6.1
Timeline
12/30/2019 🔍02/06/2020 🔍
02/06/2020 🔍
03/28/2024 🔍
Sources
Vendor: atlassian.comAdvisory: jira.atlassian.com
Status: Not defined
CVE: CVE-2019-20106 (🔍)
GCVE (CVE): GCVE-0-2019-20106
GCVE (VulDB): GCVE-100-149744
See also: 🔍
Entry
Created: 02/06/2020 12:22Updated: 03/28/2024 16:41
Changes: 02/06/2020 12:22 (39), 02/06/2020 12:27 (18), 03/28/2024 16:41 (18)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.