A user can tell curl >= 7.20.0 and <= 7.78.0 to require a su… (CVE-2021-22946, CVSS 7.5)

Summary

Vulnerability reported (CVE-2021-22946). Confidential information can be exposed externally. Exploitable via CURLOPT_USE_SSL.

Original description

The description as published by the source.

A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (--ssl-reqd on the command line orCURLOPT_USE_SSL set to CURLUSESSL_CONTROL or CURLUSESSL_ALL withlibcurl). This requirement could be bypassed if the server would return a properly crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations withoutTLS contrary to the instructions and expectations, exposing possibly sensitive data in clear text over the network.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2021-22946 has been found.
Attackers can target a specific entry point like CURLOPT_USE_SSL over the network to misuse the product.
Confidential information can be exposed externally.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2021-22946" on the vendor's site.

CVE-2021-22946 — CWE-319
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: CURLOPT_USE_SSL / CURLUSESSL_CONTROL / CURLUSESSL_ALL
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 (CWE-319) has been reported. Attackers reach the vulnerable code path via CURLOPT_USE_SSL without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions. Attack surface: CURLOPT_USE_SSL / CURLUSESSL_CONTROL / CURLUSESSL_ALL.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

Alpine Linux ALPINE-CVE-2021-22946 curl Fixed in: 7.79.0-r0

A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking...

Summary

Original description

Auto-generated summary

Response actions

Fix status by distribution

References