Categories
CVE-2023-38546 low CVSS 3.7

Vulnerability in Haxx (CVE-2023-38546)

Summary

Vulnerability in Haxx (CVE-2023-38546). Risk of unauthorized operations or information disclosure. Exploitable via none.

Original description

The description as published by the source.

This flaw allows an attacker to intentionally inject cookies into a running
program using libcurl, if the specific series of conditions are met.

libcurl performs transfers. In its API, an application creates "easy handles"
that are the individual handles for single transfers.

libcurl provides a function call that duplicates an easy handle called
curl_easy_duphandle.

If a transfer has cookies enabled when the handle is duplicated, the
cookie-enable state is also cloned - but without cloning the actual
cookies. If the source handle did not read any cookies from a specific file on
disk, the cloned version of the handle would instead store the filename as
none (using the four ASCII letters, no quotes).

Subsequent use of the cloned handle that does not explicitly set a source to
load cookies from would then inadvertently load cookies from a file named
none - if such a file exists and is readable in the current directory of the
program using libcurl, when using the correct file format of course.

Source: NIST National Vulnerability Database NVD GitHub Advisory

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-2023-38546 has been found in Haxx.
Attackers can target a specific entry point like none over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Haxx CVE-2023-38546" on the vendor's site.

CVE-2023-38546 (Haxx) — CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: none
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 Haxx. Attackers reach the vulnerable code path via none without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Haxx. Attack surface: none.

🔥 Severity

Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.

🔧 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. Run grep -r 'Haxx' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposure identify
    grep -r 'Haxx' . | grep -v node_modules

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

  2. 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

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details