← Back
ALPINE-CVE-2025-14819
Vulnerability in curl (ALPINE-CVE-2025-14819)
Summary
vulnerability in curl (ALPINE-CVE-2025-14819). Confidential information can be exposed externally. Exploitable via ``CURLSSLOPT_NO_PARTIALCHAIN``. Mitigation: upgrade to `8.19.0-r0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **ALPINE-CVE-2025-14819** has been found in curl.
Attackers can target a specific entry point like ``CURLSSLOPT_NO_PARTIALCHAIN`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade curl to **8.19.0-r0** or later.
If unsure, ask your IT team or search "curl ALPINE-CVE-2025-14819" on the vendor's site.
ALPINE-CVE-2025-14819 (curl) —
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `CURLSSLOPT_NO_PARTIALCHAIN`
Patched: `8.19.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 curl. Attackers reach the vulnerable code path via ``CURLSSLOPT_NO_PARTIALCHAIN`` without authentication.
📍 Affected scope
curl — . Attack surface: `CURLSSLOPT_NO_PARTIALCHAIN`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **8.19.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 'curl' .` 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 'curl' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `curl` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade curl to 8.19.0-r0ステージング環境で 8.19.0-r0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Alpine:v3.23
curl
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.19.0-r0"}]}]
Alpine:v3.24
curl
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.18.0-r0"}]}]