CVE-2022-1708

Vulnerability in github.com/cri-o/cri-o (CVE-2022-1708)

Summary

Vulnerability in github.com/cri-o/cri-o (CVE-2022-1708). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.24.1 or later.

Original description

The description as published by the source.

Description

An ExecSync request runs a command in a container and returns the output to the Kubelet. It is used for readiness and liveness probes within a pod. The way CRI-O runs ExecSync commands is through conmon. CRI-O asks conmon to start the process, and conmon writes the output to disk. CRI-O then reads the output and returns it to the Kubelet.

If the output of the command is large enough, it is possible to exhaust the memory (or disk usage) of the node. The following deployment is an example yaml file that will output around 8GB of ‘A’ characters, which would be written to disk by conmon and read by CRI-O.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment100
spec:
  selector:
    matchLabels:
      app: nginx
  replicas: 2
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:1.14.2
        lifecycle:
          postStart:
            exec:
              command: ["/bin/sh", "-c", "seq 1 50000000`; do echo -n 'aaaaaaaaaaaaaaaa'; done"]

Impact

It is possible for the node to be exhausted of memory or disk space, depending on the node the command is being run on. What is further problematic is that the memory and disk usage aren't attributed to the container, as this file and its processing are implementation details of CRI-O. The consequence of the exhaustion is that other services on the node, e.g. other containers, will be unable to allocate memory and…

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2022-1708 has been found in github.com/cri-o/cri-o.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/cri-o/cri-o to 1.24.1 or later.
If unsure, ask your IT team or search "github.com/cri-o/cri-o CVE-2022-1708" on the vendor's site.

CVE-2022-1708 (github.com/cri-o/cri-o) — CWE-400
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.24.1 — apply immediately
Workaround: At the time of writing, no workaround exists other than ensuring only trusted images are used.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-400) exists in github.com/cri-o/cri-o.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/cri-o/cri-o.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.24.1.

🛡️ Workaround

Workaround: At the time of writing, no workaround exists other than ensuring only trusted images are used.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/cri-o/cri-o' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'github.com/cri-o/cri-o' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/cri-o/cri-o を grep し、稼働しているサービス・バージョンを把握する。
2
Apply temporary workaround mitigate
```
At the time of writing, no workaround exists other than ensuring only trusted images are used.
```
パッチが適用されるまでの応急処置として、At the time of writing, no workaround exists other than ensuring only trusted images are used. を実施。回避策の副作用 (機能低下) を確認した上で。
3
Apply patch patch
```
Upgrade github.com/cri-o/cri-o to 1.24.1
```
ステージング環境で 1.24.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
4
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/cri-o/cri-o

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.22.5"}]}]

References

Metadata

CVE: CVE-2022-1708
GHSA: GHSA-fcm2-6c3h-pg6j
Published: 2022-06-06
First seen on SecPulse: 4 years ago
First-seen source: OSV.dev (Open Source Vulnerabilities)

CWE

CWE-400 CWE-770

Detection sources

OSV.dev (Open Source Vulnerabilities) 3 months ago