← Back
UBUNTU-CVE-2022-3775
Vulnerability in grub2-signed (UBUNTU-CVE-2022-3775)
Summary
vulnerability in grub2-signed (UBUNTU-CVE-2022-3775). Data can be tampered with by attackers. Mitigation: upgrade to `1.187.3~18.04.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **UBUNTU-CVE-2022-3775** has been found in grub2-signed.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: upgrade grub2-signed to **1.187.3~18.04.1** or later.
If unsure, ask your IT team or search "grub2-signed UBUNTU-CVE-2022-3775" on the vendor's site.
UBUNTU-CVE-2022-3775 (grub2-signed) —
Attack vector: local / no user interaction
Patched: `1.187.3~18.04.1` — 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 grub2-signed.
📍 Affected scope
grub2-signed — .
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **1.187.3~18.04.1**.
🛡️ 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 'grub2-signed' .` 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
-
1Identify exposure identify
grep -r 'grub2-signed' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `grub2-signed` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade grub2-signed to 1.187.3~18.04.1ステージング環境で 1.187.3~18.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:14.04:LTS
grub2-signed
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:16.04:LTS
grub2-signed
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:16.04:LTS
grub2-unsigned
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:18.04:LTS
grub2-signed
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.187.3~18.04.1"}]}]
Ubuntu:18.04:LTS
grub2-unsigned
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.06-2ubuntu14.1"}]}]
Ubuntu:20.04:LTS
grub2-signed
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.187.3~20.04.1"}]}]
Ubuntu:20.04:LTS
grub2-unsigned
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.06-2ubuntu14"}]}]
Ubuntu:22.04:LTS
grub2-signed
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.187.3~22.04.1"}]}]
Ubuntu:22.04:LTS
grub2-unsigned
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.06-2ubuntu14"}]}]