Atlassian FishEye/Crucible up to 4.5.0 .json access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Atlassian FishEye and Crucible up to 4.5.0. Affected by this vulnerability is an unknown functionality of the file /rest/review-coverage-chart/1.0/data/<repository_name>/.json. The manipulation leads to access control. This vulnerability is traded as CVE-2017-18035. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Atlassian FishEye and Crucible up to 4.5.0 (Programming Tool Software) and classified as critical. This issue affects an unknown code of the file /rest/review-coverage-chart/1.0/data/<repository_name>/.json. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The /rest/review-coverage-chart/1.0/data/<repository_name>/.json resource in Atlassian Fisheye and Crucible before version 4.5.1 and 4.6.0 was missing a permissions check, this allows remote attackers who do not have access to a particular repository to determine its existence and access review coverage statistics for it.
The bug was discovered 01/17/2018. The weakness was shared 02/02/2018 (Website). It is possible to read the advisory at jira.atlassian.com. The identification of this vulnerability is CVE-2017-18035 since 01/17/2018. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 16 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:rest/review-coverage-chart/1.0/data/<repository_name>/.json it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 4.5.1 or 4.6.0 eliminates this vulnerability.
The entry VDB-112738 is related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.atlassian.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.8VulDB Meta Temp Score: 5.7
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: FishEye/Crucible 4.5.1/4.6.0
Timeline
01/17/2018 🔍01/17/2018 🔍
02/02/2018 🔍
02/02/2018 🔍
02/03/2018 🔍
01/01/2020 🔍
Sources
Vendor: atlassian.comAdvisory: jira.atlassian.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-18035 (🔍)
GCVE (CVE): GCVE-0-2017-18035
GCVE (VulDB): GCVE-100-112739
See also: 🔍
Entry
Created: 02/03/2018 08:59Updated: 01/01/2020 08:21
Changes: 02/03/2018 08:59 (60), 01/01/2020 08:21 (2)
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.