LiveActive security incident?Get immediate response
CVE Record

CVE-2023-38546: This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specifi...

This flaw allows an attacker to insert cookies at will 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 en easy handle called [curl_easy_duphandle](https://curl.se/libcurl/c/curl_easy_duphandle.html). 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 file name 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. And if using the correct file format of course.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This libcurl flaw can make an application accidentally load attacker-controlled cookies from a local file named "none". It only works when a narrow set of cookie and handle-duplication conditions are present. Business impact depends on whether affected software uses libcurl cookies for sensitive sessions or trust decisions.

Executive priority

Treat as a targeted dependency remediation item, not an emergency internet-wide incident based on supplied evidence. Prioritize systems where embedded libcurl handles authentication, sessions, or automated access to sensitive services.

Technical view

When curl_easy_duphandle duplicates an easy handle with cookies enabled, libcurl clones the cookie-enabled state without cloning cookies. If no cookie file was set, the duplicate may later treat "none" as a cookie file name and load readable cookies from the current working directory.

Likely exposure

Exposure is most likely in software embedding libcurl, enabling cookies, duplicating easy handles, and running where a readable file named "none" can exist in its working directory. General curl command-line use is not established as exposed by the supplied evidence.

Exploitation context

The source bundle does not cite active exploitation, and KEV is false. Exploitation appears conditional and local-file dependent: an attacker must be able to influence or place the cookie file and benefit from injected cookies in the target application.

Researcher notes

Key uncertainty is application context. The vulnerability requires duplicated easy handles, cookie state cloning, absent cookie source, and a readable file named "none" in the process working directory. Assess impact by tracing cookie use after handle duplication.

Mitigation direction

  • Update curl/libcurl according to vendor advisories.
  • Apply OS or product security updates from affected vendors.
  • Check vendor guidance before relying on configuration-only workarounds.
  • Avoid running affected applications from writable working directories.
  • Review applications that duplicate libcurl handles with cookies enabled.

Validation and detection

  • Inventory software and appliances that bundle libcurl or curl.
  • Identify libcurl versions referenced by vendor advisories.
  • Review code for curl_easy_duphandle with cookies enabled.
  • Check runtime working directories for writable file placement risk.
  • Confirm vendor patches are installed on managed endpoints and products.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-38546 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
3ADP providers
13Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
curlcurl8.4.0, 7.9.1Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.