| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Keycloak. It has been classified as critical. Affected by this vulnerability is an unknown functionality of the component Java Process Handler. The manipulation leads to temp file. This vulnerability is uniquely identified as CVE-2021-20202. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Keycloak (unknown version). It has been rated as critical. This issue affects an unknown code block of the component Java Process Handler. The manipulation with an unknown input leads to a temp file vulnerability. Using CWE to declare the problem leads to CWE-377. Creating and using insecure temporary files can leave application and system data vulnerable to attack. Impacted is confidentiality, integrity, and availability.
The weakness was disclosed 05/12/2021. The advisory is shared at bugzilla.redhat.com. The identification of this vulnerability is CVE-2021-20202. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
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: Temp fileCWE: CWE-377
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/17/2020 🔍05/12/2021 🔍
05/12/2021 🔍
05/15/2021 🔍
Sources
Advisory: bugzilla.redhat.comStatus: Not defined
CVE: CVE-2021-20202 (🔍)
GCVE (CVE): GCVE-0-2021-20202
GCVE (VulDB): GCVE-100-174977
Entry
Created: 05/12/2021 22:29Updated: 05/15/2021 15:45
Changes: 05/12/2021 22:29 (34), 05/15/2021 15:45 (2)
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.