Vulnerability in file (ALPINE-CVE-2019-1543)

Summary

vulnerability in file (ALPINE-CVE-2019-1543). Confidential information can be exposed externally. Mitigation: upgrade to `5.36-r0` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **ALPINE-CVE-2019-1543** has been found in file. Confidential information can be exposed externally. CVSS score: ?/10. What to do: upgrade file to **5.36-r0** or later. If unsure, ask your IT team or search "file ALPINE-CVE-2019-1543" on the vendor's site.

ALPINE-CVE-2019-1543 (file) — Attack vector: remote (network-reachable) / unauthenticated / no user interaction Affected: `1.1.1 - 1.1.1b` Patched: `5.36-r0` — 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 file.

📍 Affected scope

file — Affected range: `1.1.1 - 1.1.1b`.

🔥 Severity

Severity: ?. Confidential information can be exposed externally

🔧 How to fix

Update to **5.36-r0**. (If a vulnerable version `1.1.1 - 1.1.1b` is in production, plan an immediate maintenance window.)

🛡️ 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 'file' .` 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 'file' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `file` を grep し、稼働しているサービス・バージョンを把握する。
2
Match against affected range verify
```
Confirm if version satisfies `1.1.1 - 1.1.1b`
```
Step 1 で見つかったバージョンが影響範囲 `1.1.1 - 1.1.1b` に該当するか照合。本番で稼働中ならインシデント扱い。
6
Apply patch patch
```
Upgrade file to 5.36-r0
```
ステージング環境で 5.36-r0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Alpine:v3.10 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.11 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.12 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.13 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.14 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.15 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.16 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.17 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.18 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.19 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.20 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.21 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.22 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.23 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.24 file

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.36-r0"}]}]

Alpine:v3.10 openssl