Atlassian FishEye/Crucible up to 4.8.0 Watching Setting /profile/deleteWatch.do authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Atlassian FishEye and Crucible up to 4.8.0. This vulnerability affects unknown code of the file /profile/deleteWatch.do of the component Watching Setting Handler. This manipulation causes authorization. This vulnerability is tracked as CVE-2020-4014. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability classified as critical was found in Atlassian FishEye and Crucible up to 4.8.0 (Programming Tool Software). Affected by this vulnerability is some unknown processing of the file /profile/deleteWatch.do of the component Watching Setting Handler. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. As an impact it is known to affect integrity, and availability. The summary by CVE is:
The /profile/deleteWatch.do resource in Atlassian Fisheye and Crucible before version 4.8.1 allows remote attackers to remove another user's watching settings for a repository via an improper authorization vulnerability.
The weakness was disclosed 06/01/2020. This vulnerability is known as CVE-2020-4014 since 12/30/2019. The exploitation appears to be easy. The attack can be launched remotely. Required for exploitation is a single authentication. Technical details are known, but no exploit is available.
Upgrading to version 4.8.1 eliminates this vulnerability.
The entries VDB-155921, VDB-155920, VDB-155919 and VDB-155918 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
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: AuthorizationCWE: CWE-863 / 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: FishEye/Crucible 4.8.1
Timeline
12/30/2019 🔍06/01/2020 🔍
06/02/2020 🔍
06/02/2020 🔍
Sources
Vendor: atlassian.comStatus: Not defined
CVE: CVE-2020-4014 (🔍)
GCVE (CVE): GCVE-0-2020-4014
GCVE (VulDB): GCVE-100-155917
See also: 🔍
Entry
Created: 06/02/2020 06:43Updated: 06/02/2020 06:48
Changes: 06/02/2020 06:43 (39), 06/02/2020 06:48 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.