← Back
ALPINE-CVE-2019-16760

Vulnerability in rust (ALPINE-CVE-2019-16760)

Summary

vulnerability in rust (ALPINE-CVE-2019-16760). Data can be tampered with by attackers. Exploitable via ``package``. Mitigation: upgrade to `1.26.0-r0` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **ALPINE-CVE-2019-16760** has been found in rust. Attackers can target a specific entry point like ``package`` over the network to misuse the product. Data can be tampered with by attackers. CVSS score: ?/10. What to do: upgrade rust to **1.26.0-r0** or later. If unsure, ask your IT team or search "rust ALPINE-CVE-2019-16760" on the vendor's site.
ALPINE-CVE-2019-16760 (rust) — Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `package` / `Cargo.toml` Patched: `1.26.0-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 rust. Attackers reach the vulnerable code path via ``package`` without authentication.
📍 Affected scope
rust — . Attack surface: `package` / `Cargo.toml`.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **1.26.0-r0**.
🛡️ 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 'rust' .` 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. 1
    Identify exposure identify
    grep -r 'rust' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `rust` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch
    Upgrade rust to 1.26.0-r0

    ステージング環境で 1.26.0-r0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Alpine:v3.19 rust
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.26.0-r0"}]}]
Alpine:v3.20 rust
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.26.0-r0"}]}]
Alpine:v3.21 rust
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.26.0-r0"}]}]
Alpine:v3.22 rust
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.26.0-r0"}]}]
Alpine:v3.23 rust
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.26.0-r0"}]}]
Alpine:v3.24 rust
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.26.0-r0"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →