← Back
USN-8447-3
Vulnerability in google-guest-agent (USN-8447-3)
Summary
vulnerability in google-guest-agent (USN-8447-3). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `20240716.00-0ubuntu1~16.04.0+esm3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **USN-8447-3** has been found in google-guest-agent.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade google-guest-agent to **20240716.00-0ubuntu1~16.04.0+esm3** or later.
If unsure, ask your IT team or search "google-guest-agent USN-8447-3" on the vendor's site.
USN-8447-3 (google-guest-agent) —
Patched: `20240716.00-0ubuntu1~16.04.0+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 google-guest-agent.
📍 Affected scope
google-guest-agent — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **20240716.00-0ubuntu1~16.04.0+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 'google-guest-agent' .` 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 'google-guest-agent' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `google-guest-agent` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade google-guest-agent to 20240716.00-0ubuntu1~16.04.0+esm3ステージング環境で 20240716.00-0ubuntu1~16.04.0+esm3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:16.04:LTS
google-guest-agent
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20240716.00-0ubuntu1~16.04.0+esm3"}]}]
Ubuntu:Pro:18.04:LTS
google-guest-agent
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20241011.01-0ubuntu1~18.04.0+esm3"}]}]
Ubuntu:Pro:20.04:LTS
google-guest-agent
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20250116.00-0ubuntu1~20.04.0+esm3"}]}]
Ubuntu:22.04:LTS
google-guest-agent
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20250116.00-0ubuntu1~22.04.3"}]}]
Ubuntu:24.04:LTS
google-guest-agent
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20250116.00-0ubuntu1~24.04.4"}]}]
Ubuntu:25.10
google-guest-agent
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20250506.01-0ubuntu1.2"}]}]
Ubuntu:26.04:LTS
google-guest-agent
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20250506.01-0ubuntu2.1"}]}]