Vulnerability in docker.io (UBUNTU-CVE-2023-28840)

Summary

vulnerability in docker.io (UBUNTU-CVE-2023-28840). Confidential information can be exposed externally. Exploitable via ``dockerd``. Mitigation: upgrade to `20.10.21-0ubuntu1~18.04.3+esm3` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **UBUNTU-CVE-2023-28840** has been found in docker.io. Attackers can target a specific entry point like ``dockerd`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: ?/10. What to do: upgrade docker.io to **20.10.21-0ubuntu1~18.04.3+esm3** or later. If unsure, ask your IT team or search "docker.io UBUNTU-CVE-2023-28840" on the vendor's site.

UBUNTU-CVE-2023-28840 (docker.io) — Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `dockerd` / `xt_u32` Patched: `20.10.21-0ubuntu1~18.04.3+esm3` — apply immediately 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** (unclassified) exists in docker.io. Attackers reach the vulnerable code path via ``dockerd`` without authentication.

📍 Affected scope

docker.io — . Attack surface: `dockerd` / `xt_u32`.

🔥 Severity

Severity: ?. Confidential information can be exposed externally

🔧 How to fix

Update to **20.10.21-0ubuntu1~18.04.3+esm3**.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

Response Actions (7 steps)

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

1
Identify exposure identify
```
grep -r 'docker.io' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `docker.io` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade docker.io to 20.10.21-0ubuntu1~18.04.3+esm3
```
ステージング環境で 20.10.21-0ubuntu1~18.04.3+esm3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:16.04:LTS docker.io

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:18.04:LTS docker.io

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.21-0ubuntu1~18.04.3+esm3"}]}]

Ubuntu:Pro:20.04:LTS docker.io

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.21-0ubuntu1~20.04.6+esm2"}]}]

Ubuntu:Pro:20.04:LTS docker.io-app

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:22.04:LTS docker.io

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20.10.21-0ubuntu1~22.04.7+esm2"}]}]

Ubuntu:Pro:22.04:LTS docker.io-app

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Vulnerability in docker.io (UBUNTU-CVE-2023-28840)

Summary

AI summary snake-internal / snake-material-v2

Response Actions (7 steps)

Affected packages

References

🍪 About cookies