Google Kubernetes Engine Plugin up to 0.8.0 on Jenkins YAML Parser deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Google Kubernetes Engine Plugin up to 0.8.0 on Jenkins. Impacted is an unknown function of the component YAML Parser. This manipulation causes deserialization. This vulnerability is tracked as CVE-2020-2121. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as critical was found in Google Kubernetes Engine Plugin up to 0.8.0 on Jenkins (Virtualization Software). Affected by this vulnerability is an unknown functionality of the component YAML Parser. The manipulation with an unknown input leads to a deserialization vulnerability. The CWE definition for the vulnerability is CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Jenkins Google Kubernetes Engine Plugin 0.8.0 and earlier does not configure its YAML parser to prevent the instantiation of arbitrary types, resulting in a remote code execution vulnerability.
The weakness was disclosed 02/12/2020 (oss-sec). It is possible to read the advisory at openwall.com. This vulnerability is known as CVE-2020-2121 since 12/05/2019. The exploitation appears to be easy. The attack can be launched remotely. The successful exploitation needs a single authentication. The technical details are unknown and an exploit is not publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-150055, VDB-150056, VDB-150057 and VDB-150058 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
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/05/2019 🔍02/12/2020 🔍
02/13/2020 🔍
02/13/2020 🔍
Sources
Advisory: openwall.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-2121 (🔍)
GCVE (CVE): GCVE-0-2020-2121
GCVE (VulDB): GCVE-100-150067
See also: 🔍
Entry
Created: 02/13/2020 08:19Updated: 02/13/2020 08:24
Changes: 02/13/2020 08:19 (39), 02/13/2020 08:24 (18)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.