Atlassian JIRA Server/Data Center up to 8.13.14/8.20.2 Jira-importers-plugin CsvFieldMappingsPage.jspa cross-site request forgery

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

Summaryinfo

A vulnerability was found in Atlassian JIRA Server and Data Center up to 8.13.14/8.20.2. It has been classified as problematic. Affected is an unknown function of the file CsvFieldMappingsPage.jspa of the component Jira-importers-plugin. This manipulation causes cross-site request forgery. This vulnerability appears as CVE-2021-43941. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Atlassian JIRA Server and Data Center up to 8.13.14/8.20.2 (Bug Tracking Software). It has been declared as problematic. Affected by this vulnerability is an unknown code block of the file CsvFieldMappingsPage.jspa of the component Jira-importers-plugin. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity.

The weakness was presented 02/15/2022. The advisory is shared at jira.atlassian.com. This vulnerability is known as CVE-2021-43941 since 11/16/2021. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

Upgrading to version 8.13.15 or 8.20.3 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: 4.3
VulDB Meta Temp Score: 4.1

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

CVSSv2info

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

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

Exploitinginfo

Class: Cross-site request forgery
CWE: CWE-352 / CWE-862 / CWE-863
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.13.15/8.20.3

Timelineinfo

11/16/2021 🔍
02/15/2022 +91 days 🔍
02/15/2022 +0 days 🔍
02/18/2022 +3 days 🔍

Sourcesinfo

Vendor: atlassian.com

Advisory: jira.atlassian.com
Status: Confirmed

CVE: CVE-2021-43941 (🔍)
GCVE (CVE): GCVE-0-2021-43941
GCVE (VulDB): GCVE-100-193093

Entryinfo

Created: 02/15/2022 07:44
Updated: 02/18/2022 08:35
Changes: 02/15/2022 07:44 (41), 02/18/2022 08:35 (1)
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!