CVE-2022-1708

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 3.2% (87th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation3.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
3.2%
EPSS %ILE
87th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 7, 2022

Last Modified

November 21, 2024

References (3)

Patch Availability(9)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/cri-o/cri-o1.24.0
  • 1.24.0 up to 1.24.1: fixed in 1.24.1
  • 1.23.0 up to 1.23.3: fixed in 1.23.3
  • every version up to 1.22.5: fixed in 1.22.5
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 9× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 92 of 172 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 8 repeat rows among the latest 100 are merged into the row they repeat. The 80 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 19:03 UTCEG score recompute
  2. 2026-10-12 16:30 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  3. 2026-10-11 23:29 UTCEG score recompute
  4. 2026-10-11 13:44 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  5. 2026-10-10 19:56 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  6. 2026-10-09 20:04 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  7. 2026-10-08 16:40 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  8. 2026-10-07 23:45 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  9. 2026-10-06 15:14 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  10. 2026-10-05 17:40 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  11. 2026-10-04 23:19 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  12. 2026-10-03 14:22 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  13. 2026-10-02 16:23 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  14. 2026-09-30 15:47 UTCEG score recompute
  15. 2026-09-30 15:00 UTCEPSS rescoreEPSS 3.2% · 87th percentile
  16. 2026-09-29 15:15 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  17. 2026-09-28 13:47 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  18. 2026-09-26 15:54 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  19. 2026-09-26 00:21 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  20. 2026-09-24 20:46 UTCOSV refresh
  21. 2026-09-24 14:00 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  22. 2026-09-23 13:45 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  23. 2026-09-22 14:44 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  24. 2026-09-21 20:28 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  25. 2026-09-20 20:13 UTCEPSS rescoreEPSS 3.1% · 87th percentile
Show 67 more
  1. 2026-09-19 15:38 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  2. 2026-09-18 19:24 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  3. 2026-09-17 19:23 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  4. 2026-09-16 14:05 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  5. 2026-09-15 03:06 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  6. 2026-09-12 14:57 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  7. 2026-09-11 14:49 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  8. 2026-09-11 09:33 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  9. 2026-09-08 21:57 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  10. 2026-09-07 15:58 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  11. 2026-09-06 13:45 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  12. 2026-09-05 15:25 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  13. 2026-09-05 12:30 UTCOSV refresh
  14. 2026-09-04 13:57 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  15. 2026-09-04 05:03 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  16. 2026-09-02 14:09 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  17. 2026-09-01 13:51 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  18. 2026-08-30 19:14 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  19. 2026-08-30 01:19 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  20. 2026-08-28 21:38 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  21. 2026-08-27 14:22 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  22. 2026-08-26 14:43 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  23. 2026-08-25 13:46 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  24. 2026-08-24 14:13 UTCEPSS rescoreEPSS 3.1% · 86th percentile
  25. 2026-08-21 23:46 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  26. 2026-08-20 22:52 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  27. 2026-08-19 17:01 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  28. 2026-08-18 23:10 UTCOSV refresh
  29. 2026-08-18 13:45 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  30. 2026-08-17 13:44 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  31. 2026-08-16 14:53 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  32. 2026-08-16 02:11 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  33. 2026-08-15 01:27 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  34. 2026-08-13 21:57 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  35. 2026-08-12 13:48 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  36. 2026-08-11 13:38 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  37. 2026-08-09 13:44 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  38. 2026-08-08 16:34 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  39. 2026-08-07 16:24 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  40. 2026-08-06 13:44 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  41. 2026-08-05 19:15 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  42. 2026-08-04 15:06 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  43. 2026-08-04 10:34 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  44. 2026-08-03 18:57 UTCOSV refresh
  45. 2026-08-03 10:33 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  46. 2026-08-02 02:24 UTCEPSS rescoreEPSS 3.0% · 86th percentile
  47. 2026-08-01 04:13 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  48. 2026-07-30 16:25 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  49. 2026-07-30 01:28 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  50. 2026-07-28 15:33 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  51. 2026-07-26 14:52 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  52. 2026-07-25 14:15 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  53. 2026-07-24 14:15 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  54. 2026-07-23 14:16 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  55. 2026-07-23 02:07 UTCEG score recompute
  56. 2026-07-22 22:53 UTCEG score recompute
  57. 2026-07-22 14:06 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  58. 2026-07-21 15:22 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  59. 2026-07-20 17:05 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  60. 2026-07-19 14:29 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  61. 2026-07-19 02:27 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  62. 2026-07-18 10:02 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  63. 2026-07-17 08:50 UTCOSV refresh
  64. 2026-07-16 17:00 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  65. 2026-07-15 16:55 UTCEPSS rescoreEPSS 2.8% · 85th percentile
  66. 2026-07-15 01:58 UTCEPSS rescoreEPSS 2.8% · 84th percentile
  67. 2026-07-13 22:27 UTCEPSS rescoreEPSS 2.8% · 84th percentile

Frequently asked(5)

What is CVE-2022-1708?
CVE-2022-1708 is a high-severity vulnerability; its CVE record was published on June 7, 2022. 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…
When was the CVE record for CVE-2022-1708 published?
The CVE record for CVE-2022-1708 was published on June 7, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-1708 actively exploited?
CVE-2022-1708 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.2% probability of exploitation in the next 30 days (87th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-1708?
CVE-2022-1708 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2022-1708?
A fix for CVE-2022-1708 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-1708 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-1708

Explore →

Is Your Infrastructure Affected by CVE-2022-1708?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.