Atlassian JIRA Server/Data Center up to 8.5.11/8.13.3 Cookie missing secure attribute
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Atlassian JIRA Server and Data Center up to 8.5.11/8.13.3. This affects an unknown part of the component Cookie Handler. This manipulation causes missing secure attribute. This vulnerability is registered as CVE-2021-26076. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability has been found in Atlassian JIRA Server and Data Center up to 8.5.11/8.13.3 (Bug Tracking Software) and classified as problematic. Affected by this vulnerability is an unknown code of the component Cookie Handler. The manipulation with an unknown input leads to a missing secure attribute vulnerability. The CWE definition for the vulnerability is CWE-614. The Secure attribute for sensitive cookies in HTTPS sessions is not set, which could cause the user agent to send those cookies in plaintext over an HTTP session. As an impact it is known to affect confidentiality.
The weakness was published 04/15/2021. The advisory is shared at jira.atlassian.com. This vulnerability is known as CVE-2021-26076. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1539 for this issue.
Upgrading to version 8.5.12, 8.13.4 or 8.15.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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: 3.7VulDB Meta Temp Score: 3.6
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
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: Missing secure attributeCWE: CWE-614 / CWE-1004 / CWE-732
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 Server/Data Center 8.5.12/8.13.4/8.15.0
Timeline
01/25/2021 🔍04/15/2021 🔍
04/15/2021 🔍
04/21/2021 🔍
Sources
Vendor: atlassian.comAdvisory: jira.atlassian.com
Status: Confirmed
CVE: CVE-2021-26076 (🔍)
GCVE (CVE): GCVE-0-2021-26076
GCVE (VulDB): GCVE-100-173065
Entry
Created: 04/15/2021 11:38Updated: 04/21/2021 08:02
Changes: 04/15/2021 11:38 (39), 04/21/2021 08:02 (5)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.