| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Garden up to 0.12.64/0.13.16. This impacts an unknown function. The manipulation leads to deserialization. This vulnerability is listed as CVE-2023-44392. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Garden up to 0.12.64/0.13.16. It has been rated as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Garden provides automation for Kubernetes development and testing. Prior tov ersions 0.13.17 and 0.12.65, Garden has a dependency on the cryo library, which is vulnerable to code injection due to an insecure implementation of deserialization. Garden stores serialized objects using cryo in the Kubernetes `ConfigMap` resources prefixed with `test-result` and `run-result` to cache Garden test and run results. These `ConfigMaps` are stored either in the `garden-system` namespace or the configured user namespace. When a user invokes the command `garden test` or `garden run` objects stored in the `ConfigMap` are retrieved and deserialized. This can be used by an attacker with access to the Kubernetes cluster to store malicious objects in the `ConfigMap`, which can trigger a remote code execution on the users machine when cryo deserializes the object. In order to exploit this vulnerability, an attacker must have access to the Kubernetes cluster used to deploy garden remote environments. Further, a user must actively invoke either a `garden test` or `garden run` which has previously cached results. The issue has been patched in Garden versions `0.13.17` (Bonsai) and `0.12.65` (Acorn). Only Garden versions prior to these are vulnerable. No known workarounds are available.
The weakness was presented 10/10/2023 as GHSA-hm75-6vc9-8rpr. The advisory is shared at github.com. The identification of this vulnerability is CVE-2023-44392 since 09/28/2023. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 0.12.65 or 0.13.17 eliminates this vulnerability. Applying the patch 3117964da40d3114f129a6131b4ada89eaa4eb8c is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 0.12.0
- 0.12.1
- 0.12.2
- 0.12.3
- 0.12.4
- 0.12.5
- 0.12.6
- 0.12.7
- 0.12.8
- 0.12.9
- 0.12.10
- 0.12.11
- 0.12.12
- 0.12.13
- 0.12.14
- 0.12.15
- 0.12.16
- 0.12.17
- 0.12.18
- 0.12.19
- 0.12.20
- 0.12.21
- 0.12.22
- 0.12.23
- 0.12.24
- 0.12.25
- 0.12.26
- 0.12.27
- 0.12.28
- 0.12.29
- 0.12.30
- 0.12.31
- 0.12.32
- 0.12.33
- 0.12.34
- 0.12.35
- 0.12.36
- 0.12.37
- 0.12.38
- 0.12.39
- 0.12.40
- 0.12.41
- 0.12.42
- 0.12.43
- 0.12.44
- 0.12.45
- 0.12.46
- 0.12.47
- 0.12.48
- 0.12.49
- 0.12.50
- 0.12.51
- 0.12.52
- 0.12.53
- 0.12.54
- 0.12.55
- 0.12.56
- 0.12.57
- 0.12.58
- 0.12.59
- 0.12.60
- 0.12.61
- 0.12.62
- 0.12.63
- 0.12.64
- 0.13.0
- 0.13.1
- 0.13.2
- 0.13.3
- 0.13.4
- 0.13.5
- 0.13.6
- 0.13.7
- 0.13.8
- 0.13.9
- 0.13.10
- 0.13.11
- 0.13.12
- 0.13.13
- 0.13.14
- 0.13.15
- 0.13.16
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.0
NVD Vector: 🔍
CNA Base Score: 8.2
CNA Vector (GitHub, Inc.): 🔍
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: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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: Garden 0.12.65/0.13.17
Patch: 3117964da40d3114f129a6131b4ada89eaa4eb8c
Timeline
09/28/2023 🔍10/10/2023 🔍
10/10/2023 🔍
10/28/2023 🔍
Sources
Advisory: GHSA-hm75-6vc9-8rprStatus: Confirmed
CVE: CVE-2023-44392 (🔍)
GCVE (CVE): GCVE-0-2023-44392
GCVE (VulDB): GCVE-100-241613
Entry
Created: 10/10/2023 08:39Updated: 10/28/2023 07:15
Changes: 10/10/2023 08:39 (50), 10/28/2023 07:15 (11)
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.