| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in go-yaml up to 2.2.3. It has been classified as problematic. The impacted element is an unknown function of the component YAML Document Handler. This manipulation causes resource consumption. The identification of this vulnerability is CVE-2022-3064. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability has been found in go-yaml up to 2.2.3 and classified as problematic. Affected by this vulnerability is an unknown code block of the component YAML Document Handler. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:
Parsing malicious or large YAML documents can consume excessive amounts of CPU or memory.
The weakness was shared 12/28/2022 as f221b8435cfb71e54062f6c6e99e9ade30b124d5. The advisory is shared at github.com. This vulnerability is known as CVE-2022-3064 since 08/30/2022. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 212040 (RHEL 9 : rhc (RHSA-2024:10759)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 2.2.4 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch f221b8435cfb71e54062f6c6e99e9ade30b124d5 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.
The vulnerability is also documented in the databases at Tenable (212040) and CERT Bund (WID-SEC-2023-0468). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Red Hat Enterprise Linux
- Fedora Linux
- Oracle Linux
- Dell NetWorker
- Red Hat OpenStack
- Red Hat OpenShift
- RESF Rocky Linux
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
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 |
Nessus ID: 212040
Nessus Name: RHEL 9 : rhc (RHSA-2024:10759)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: go-yaml 2.2.4
Patch: f221b8435cfb71e54062f6c6e99e9ade30b124d5
Timeline
08/30/2022 🔍12/28/2022 🔍
12/28/2022 🔍
11/30/2025 🔍
Sources
Advisory: f221b8435cfb71e54062f6c6e99e9ade30b124d5Status: Confirmed
CVE: CVE-2022-3064 (🔍)
GCVE (CVE): GCVE-0-2022-3064
GCVE (VulDB): GCVE-100-216949
CERT Bund: WID-SEC-2023-0468 - Red Hat OpenShift: Schwachstelle ermöglicht Denial of Service
Entry
Created: 12/28/2022 09:42Updated: 11/30/2025 13:57
Changes: 12/28/2022 09:42 (43), 01/25/2023 14:45 (11), 12/04/2024 06:02 (17), 11/30/2025 13:57 (7)
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.