CVE-2022-1708
Last modified
CVE-2022-1708 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to the Kube API. The ExecSync request runs commands in a container and logs the output of the command. EPSS estimates a 2.80% chance of exploitation in the next 30 days.
Description
A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to the Kube API. The ExecSync request runs commands in a container and logs the output of the command. This output is then read by CRI-O after command execution, and it is read in a manner where the entire file corresponding to the output of the command is read in. Thus, if the output of the command is large it is possible to exhaust the memory or the disk space of the node when CRI-O reads the output of the command. The highest threat from this vulnerability is system availability.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Kubernetes | Cri-O | < 1.19.7 |
| Kubernetes | Cri-O | >= 1.20.0, < 1.20.8 |
| Kubernetes | Cri-O | >= 1.21.0, < 1.21.8 |
| Kubernetes | Cri-O | >= 1.22.0, < 1.22.5 |
| Kubernetes | Cri-O | >= 1.23.0, < 1.23.3 |
| Kubernetes | Cri-O | 1.24.0 |
| Fedoraproject | Fedora | 36 |
| Redhat | Openshift Container Platform | 3.11 |
| Redhat | Openshift Container Platform | 4.0 |
| Redhat | Openshift Container Platform | 4.9 |
| Redhat | Openshift Container Platform | 4.10 |
| Redhat | Enterprise Linux | 7.0 |
| Redhat | Enterprise Linux | 8.0 |
| Redhat | Enterprise Linux | 9.0 |
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2085361Issue Tracking, Third Party Advisory
- https://github.com/cri-o/cri-o/security/advisories/GHSA-fcm2-6c3h-pg6jExploit, Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2085361Issue Tracking, Third Party Advisory
- https://github.com/cri-o/cri-o/security/advisories/GHSA-fcm2-6c3h-pg6jExploit, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-1708?
How severe is CVE-2022-1708?
How do I fix CVE-2022-1708?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-1702SonicWall SMA1000 series firmware 12.4.0, 12.4.1-02965 and e…6.1
- CVE-2022-1703Improper neutralization of special elements in the SonicWall…8.8
- CVE-2022-1704Due to an XML external entity reference, the software parses…9.8
- CVE-2022-1705Acceptance of some invalid Transfer-Encoding headers in the …6.5
- CVE-2022-1706A vulnerability was found in Ignition where ignition configs…6.5
- CVE-2022-1707The Google Tag Manager for WordPress plugin for WordPress is…6.1
- CVE-2022-1709The Throws SPAM Away WordPress plugin before 3.3.1 does not …4.3
- CVE-2022-1710The Appointment Hour Booking WordPress plugin before 1.3.56 …4.8
- CVE-2022-1711Server-Side Request Forgery (SSRF) in GitHub repository jgra…7.5
- CVE-2022-1712The LiveSync for WordPress plugin through 1.0 does not have …4.3
- CVE-2022-1713SSRF on /proxy in GitHub repository jgraph/drawio prior to 1…7.5
- CVE-2022-1714Out-of-bounds Read in GitHub repository radareorg/radare2 pr…7.1
Are you affected by CVE-2022-1708?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST