Kibana up to 6.8.14/7.11.x Session Timeout session expiration
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 1.00 |
Summary
A vulnerability was found in Kibana up to 6.8.14/7.11.x. It has been rated as critical. The affected element is an unknown function of the component Session Timeout Handler. The manipulation leads to session expiration. This vulnerability is traded as CVE-2021-22136. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in Kibana up to 6.8.14/7.11.x. It has been rated as problematic. This issue affects an unknown function of the component Session Timeout Handler. The manipulation with an unknown input leads to a session expiration vulnerability. Using CWE to declare the problem leads to CWE-613. According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." Impacted is confidentiality.
The weakness was shared 05/14/2021. The advisory is shared at discuss.elastic.co. The identification of this vulnerability is CVE-2021-22136. Neither technical details nor an exploit are publicly available.
Upgrading to version 6.8.15 or 7.12.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
- 6.8.0
- 6.8.1
- 6.8.2
- 6.8.3
- 6.8.4
- 6.8.5
- 6.8.6
- 6.8.7
- 6.8.8
- 6.8.9
- 6.8.10
- 6.8.11
- 6.8.12
- 6.8.13
- 6.8.14
- 7.0
- 7.1
- 7.2
- 7.3
- 7.4
- 7.5
- 7.6
- 7.7
- 7.8
- 7.9
- 7.10
- 7.11
License
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: Session expirationCWE: CWE-613
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: Kibana 6.8.15/7.12.0
Timeline
01/04/2021 🔍05/14/2021 🔍
05/14/2021 🔍
05/16/2021 🔍
Sources
Advisory: discuss.elastic.coStatus: Confirmed
CVE: CVE-2021-22136 (🔍)
GCVE (CVE): GCVE-0-2021-22136
GCVE (VulDB): GCVE-100-175049
Entry
Created: 05/14/2021 07:05Updated: 05/16/2021 11:04
Changes: 05/14/2021 07:05 (37), 05/16/2021 11:04 (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.