Atlassian Crowd up to 2.10.0 LDAP Password Response information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Atlassian Crowd up to 2.10.0. This affects an unknown part of the component LDAP Password Handler. The manipulation as part of Response results in information disclosure. This vulnerability was named CVE-2016-10740. The attack may be performed from remote. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability was found in Atlassian Crowd up to 2.10.0. It has been classified as problematic. Affected is an unknown part of the component LDAP Password Handler. The manipulation as part of a Response 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. CVE summarizes:
Various resources in Atlassian Crowd before version 2.10.1 allow remote attackers with administration rights to learn the passwords of configured LDAP directories by examining the responses to requests for these resources.
The bug was discovered 03/08/2018. The weakness was presented 01/29/2019 (Website). The advisory is shared for download at jira.atlassian.com. This vulnerability is traded as CVE-2016-10740 since 01/28/2019. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is necessary for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.
The vulnerability was handled as a non-public zero-day exploit for at least 326 days. During that time the estimated underground price was around $0-$5k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 13406 (Atlassian Crowd Sensitive Data Exposure Vulnerability).
Upgrading to version 2.10.1 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.8VulDB Meta Temp Score: 3.7
VulDB Base Score: 2.7
VulDB Temp Score: 2.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.9
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 |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Atlassian Crowd 2.10.1
Timeline
03/08/2018 🔍01/28/2019 🔍
01/28/2019 🔍
01/29/2019 🔍
01/30/2019 🔍
05/06/2020 🔍
Sources
Advisory: jira.atlassian.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2016-10740 (🔍)
GCVE (CVE): GCVE-0-2016-10740
GCVE (VulDB): GCVE-100-130308
Entry
Created: 01/30/2019 07:49Updated: 05/06/2020 16:22
Changes: 01/30/2019 07:49 (61), 05/06/2020 16:22 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.