Atlassian Bamboo up to 6.2.2 Plan Configure Branches cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Atlassian Bamboo up to 6.2.2. It has been rated as problematic. Affected is an unknown function of the component Plan Configure Branches. Performing a manipulation results in cross site scripting. This vulnerability is cataloged as CVE-2017-18082. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in Atlassian Bamboo up to 6.2.2. It has been classified as problematic. This affects an unknown function of the component Plan Configure Branches. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:
The plan configure branches resource in Atlassian Bamboo before version 6.2.3 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability through the name of a branch.
The bug was discovered 02/02/2018. The weakness was shared 02/02/2018 (Website). The advisory is shared at jira.atlassian.com. This vulnerability is uniquely identified as CVE-2017-18082 since 02/01/2018. It is possible to initiate the attack remotely. The successful exploitation requires a authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
Upgrading to version 6.2.3 eliminates this vulnerability.
The entries VDB-112748, VDB-112747, VDB-112746 and VDB-112745 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
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.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
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: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
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: Bamboo 6.2.3
Timeline
02/01/2018 🔍02/02/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-18082 (🔍)
GCVE (CVE): GCVE-0-2017-18082
GCVE (VulDB): GCVE-100-112749
See also: 🔍
Entry
Created: 02/03/2018 09:01Updated: 01/01/2020 08:51
Changes: 02/03/2018 09:01 (58), 01/01/2020 08:51 (2)
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.