Atlassian JIRA Server/Data Center up to 8.5.13/8.13.5/8.16.0 REST API temporary information disclosure

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.9$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Atlassian JIRA Server and Data Center up to 8.5.13/8.13.5/8.16.0. This affects an unknown part of the file /rest/api/latest/user/avatar/temporary of the component REST API. Performing a manipulation results in information disclosure. This vulnerability is reported as CVE-2021-26081. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Atlassian JIRA Server and Data Center up to 8.5.13/8.13.5/8.16.0 (Bug Tracking Software). It has been classified as problematic. This affects an unknown code of the file /rest/api/latest/user/avatar/temporary of the component REST API. 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 weakness was disclosed 07/20/2021. The advisory is shared at jira.atlassian.com. This vulnerability is uniquely identified as CVE-2021-26081. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 8.5.14, 8.6.0, 8.13.6, 8.14.0 or 8.16.1 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 4.9

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.3
NVD Vector: 🔍

CNA Base Score: 5.3
CNA Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: JIRA Server/Data Center 8.5.14/8.6.0/8.13.6/8.14.0/8.16.1

Timelineinfo

01/25/2021 🔍
07/20/2021 +175 days 🔍
07/20/2021 +0 days 🔍
10/11/2024 +1179 days 🔍

Sourcesinfo

Vendor: atlassian.com

Advisory: jira.atlassian.com
Status: Confirmed

CVE: CVE-2021-26081 (🔍)
GCVE (CVE): GCVE-0-2021-26081
GCVE (VulDB): GCVE-100-178917

Entryinfo

Created: 07/20/2021 10:12
Updated: 10/11/2024 23:47
Changes: 07/20/2021 10:12 (40), 07/22/2021 14:07 (2), 10/11/2024 23:47 (42)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!