← Back
UBUNTU-CVE-2019-3901
Vulnerability in linux-lts-xenial (UBUNTU-CVE-2019-3901)
Summary
vulnerability in linux-lts-xenial (UBUNTU-CVE-2019-3901). Confidential information can be exposed externally. Mitigation: upgrade to `4.4.0-28.47~14.04.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **UBUNTU-CVE-2019-3901** has been found in linux-lts-xenial.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade linux-lts-xenial to **4.4.0-28.47~14.04.1** or later.
If unsure, ask your IT team or search "linux-lts-xenial UBUNTU-CVE-2019-3901" on the vendor's site.
UBUNTU-CVE-2019-3901 (linux-lts-xenial) —
Attack vector: local / no user interaction
Patched: `4.4.0-28.47~14.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 linux-lts-xenial.
📍 Affected scope
linux-lts-xenial — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **4.4.0-28.47~14.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 'linux-lts-xenial' .` 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 'linux-lts-xenial' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `linux-lts-xenial` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade linux-lts-xenial to 4.4.0-28.47~14.04.1ステージング環境で 4.4.0-28.47~14.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:14.04:LTS
linux-lts-xenial
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-28.47~14.04.1"}]}]
Ubuntu:Pro:14.04:LTS
linux
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:16.04:LTS
linux
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-28.47"}]}]
Ubuntu:16.04:LTS
linux-raspi2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1016.22"}]}]
Ubuntu:16.04:LTS
linux-snapdragon
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.0-1019.22"}]}]
Ubuntu:20.04:LTS
linux-azure-fde
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:Pro:20.04:LTS
linux-azure-fde-5.15
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:20.04:LTS
linux-gke
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:20.04:LTS
linux-gkeop
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:20.04:LTS
linux-gkeop-5.15
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:20.04:LTS
linux-raspi2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:20.04:LTS
linux-riscv
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:22.04:LTS
linux-intel-iot-realtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:22.04:LTS
linux-realtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:22.04:LTS
linux-riscv
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:24.04:LTS
linux-azure-6.11
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:24.04:LTS
linux-gcp-6.11
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:24.04:LTS
linux-hwe-6.11
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:24.04:LTS
linux-lowlatency-hwe-6.11
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:24.04:LTS
linux-raspi-realtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]