Atlassian JIRA Server/Data Center up to 7.6.16/7.13.8/8.4.1 Comment information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Atlassian JIRA Server and Data Center up to 7.6.16/7.13.8/8.4.1. It has been rated as problematic. The impacted element is an unknown function of the component Comment Handler. Performing a manipulation results in information disclosure. This vulnerability is known as CVE-2019-20410. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in Atlassian JIRA Server and Data Center up to 7.6.16/7.13.8/8.4.1 (Bug Tracking Software). This affects an unknown function of the component Comment Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
Affected versions of Atlassian Jira Server and Data Center allow remote attackers to view sensitive information via an Information Disclosure vulnerability in the comment restriction feature. The affected versions are before version 7.6.17, from version 7.7.0 before 7.13.9, and from version 8.0.0 before 8.4.2.
The weakness was published 06/29/2020 (Website). It is possible to read the advisory at jira.atlassian.com. This vulnerability is uniquely identified as CVE-2019-20410 since 01/23/2020. The exploitability is told to be easy. It is possible to initiate the attack remotely. The successful exploitation requires a authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Upgrading to version 7.6.17, 7.13.9 or 8.4.2 eliminates this vulnerability.
Similar entries are available at VDB-157399, VDB-157398, VDB-157397 and VDB-157396. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 7.6.0
- 7.6.1
- 7.6.2
- 7.6.3
- 7.6.4
- 7.6.5
- 7.6.6
- 7.6.7
- 7.6.8
- 7.6.9
- 7.6.10
- 7.6.11
- 7.6.12
- 7.6.13
- 7.6.14
- 7.6.15
- 7.6.16
- 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
- 8.4.0
- 8.4.1
License
Website
- Vendor: https://www.atlassian.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: Information disclosureCWE: CWE-200 / CWE-284 / 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.6.17/7.13.9/8.4.2
Timeline
01/23/2020 🔍06/29/2020 🔍
06/29/2020 🔍
06/29/2020 🔍
Sources
Vendor: atlassian.comAdvisory: jira.atlassian.com
Status: Not defined
CVE: CVE-2019-20410 (🔍)
GCVE (CVE): GCVE-0-2019-20410
GCVE (VulDB): GCVE-100-157395
See also: 🔍
Entry
Created: 06/29/2020 12:56Updated: 06/29/2020 13:01
Changes: 06/29/2020 12:56 (40), 06/29/2020 13:01 (18)
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.