Atlassian JIRA Server/Data Center up to 8.19.0 Roles Settings roles improper authentication

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.
7.3$0-$5k0.00

Summaryinfo

A vulnerability has been found in Atlassian JIRA Server and Data Center up to 8.19.0 and classified as critical. This affects an unknown function of the file /plugins/servlet/project-config/PROJECT/roles of the component Roles Settings Handler. Performing a manipulation results in improper authentication. This vulnerability is identified as CVE-2021-41311. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Atlassian JIRA Server and Data Center up to 8.19.0 (Bug Tracking Software). It has been classified as critical. This affects an unknown part of the file /plugins/servlet/project-config/PROJECT/roles of the component Roles Settings Handler. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was released 12/08/2021. The advisory is shared at jira.atlassian.com. This vulnerability is uniquely identified as CVE-2021-41311 since 09/16/2021. Technical details are known, but no exploit is available.

Upgrading to version 8.19.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: 7.4
VulDB Meta Temp Score: 7.3

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CNA Base Score: 7.5
CNA Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Improper authentication
CWE: CWE-287
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.19.1

Timelineinfo

09/16/2021 🔍
12/08/2021 +83 days 🔍
12/08/2021 +0 days 🔍
10/10/2024 +1037 days 🔍

Sourcesinfo

Vendor: atlassian.com

Advisory: jira.atlassian.com
Status: Confirmed

CVE: CVE-2021-41311 (🔍)
GCVE (CVE): GCVE-0-2021-41311
GCVE (VulDB): GCVE-100-187701

Entryinfo

Created: 12/08/2021 08:00
Updated: 10/10/2024 17:03
Changes: 12/08/2021 08:00 (41), 12/10/2021 20:52 (1), 12/10/2021 21:00 (1), 10/10/2024 17:03 (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!