← Back

USN-4210-1

Vulnerability in linux-aws-hwe (USN-4210-1)

Summary

vulnerability in linux-aws-hwe (USN-4210-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `4.15.0-1056.58~16.04.1` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **USN-4210-1** has been found in linux-aws-hwe. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade linux-aws-hwe to **4.15.0-1056.58~16.04.1** or later. If unsure, ask your IT team or search "linux-aws-hwe USN-4210-1" on the vendor's site.

USN-4210-1 (linux-aws-hwe) — Patched: `4.15.0-1056.58~16.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-aws-hwe.

📍 Affected scope

linux-aws-hwe — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

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

Affected packages

Ubuntu:16.04:LTS linux-aws-hwe

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1056.58~16.04.1"}]}]

Ubuntu:16.04:LTS linux-gcp

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1050.53"}]}]

Ubuntu:16.04:LTS linux-hwe

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-72.81~16.04.1"}]}]

Ubuntu:16.04:LTS linux-oracle

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1030.33~16.04.1"}]}]

Ubuntu:18.04:LTS linux

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-72.81"}]}]

Ubuntu:18.04:LTS linux-aws

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1056.58"}]}]

Ubuntu:18.04:LTS linux-gke-4.15

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1049.52"}]}]

Ubuntu:18.04:LTS linux-kvm

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1051.51"}]}]

Ubuntu:18.04:LTS linux-oem

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1065.75"}]}]

Ubuntu:18.04:LTS linux-oracle

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1030.33"}]}]

Ubuntu:18.04:LTS linux-raspi2

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1052.56"}]}]

Ubuntu:18.04:LTS linux-snapdragon

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-1069.76"}]}]

References

advisory https://ubuntu.com/security/notices/USN-4210-1
report https://ubuntu.com/security/CVE-2019-16746
report https://ubuntu.com/security/CVE-2019-17075
report https://ubuntu.com/security/CVE-2019-17133
report https://ubuntu.com/security/CVE-2019-19060
report https://ubuntu.com/security/CVE-2019-19065
report https://ubuntu.com/security/CVE-2019-19075