Atlassian Jira Service Management Server/Data Center up to 4.20.x Object Import Configuration information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Atlassian Jira Service Management Server and Data Center up to 4.20.x. The affected element is an unknown function of the component Object Import Configuration Handler. This manipulation causes information disclosure. This vulnerability is tracked as CVE-2021-43951. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability has been found in Atlassian Jira Service Management Server and Data Center up to 4.20.x (Bug Tracking Software) and classified as problematic. Affected by this vulnerability is some unknown functionality of the component Object Import Configuration Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.
The weakness was disclosed 01/10/2022. The advisory is shared at jira.atlassian.com. This vulnerability is known as CVE-2021-43951 since 11/16/2021. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 4.21.0 eliminates this vulnerability.
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.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Information disclosureCWE: 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-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: Jira Service Management Server/Data Center 4.21.0
Timeline
11/16/2021 🔍01/10/2022 🔍
01/10/2022 🔍
01/12/2022 🔍
Sources
Vendor: atlassian.comAdvisory: jira.atlassian.com
Status: Confirmed
CVE: CVE-2021-43951 (🔍)
GCVE (CVE): GCVE-0-2021-43951
GCVE (VulDB): GCVE-100-189877
Entry
Created: 01/10/2022 19:10Updated: 01/12/2022 10:40
Changes: 01/10/2022 19:10 (40), 01/12/2022 10:40 (1)
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.