CVE-2023-46219: When saving HSTS data to an excessively long file name, curl could end up
removing all contents, making sub...
When saving HSTS data to an excessively long file name, curl could end up
removing all contents, making subsequent requests using that file unaware of
the HSTS status they should otherwise use.
Security readout for executives and security teams
Plain-English summary
curl could erase its saved HSTS state when asked to save it using an excessively long file name. Later connections using that file may forget which sites require HTTPS, weakening an expected transport-security protection.
Executive priority
Handle through normal vulnerability management, with priority for systems where curl enforces HTTPS policy for sensitive automated traffic. This is not presented as actively exploited, but it can silently weaken transport-security expectations.
Technical view
CVE-2023-46219 is an HSTS persistence flaw in curl. A long HSTS file name can cause the saved HSTS data to be emptied, so later requests no longer apply stored HSTS status. The source bundle lists curl 7.84.0 and 8.4.0 as affected and rates this CVSS 5.3 medium.
Likely exposure
Exposure is most relevant where curl is configured to use persistent HSTS data and the HSTS file path or name can become excessively long. Typical one-off curl use without HSTS persistence is less exposed based on the provided description.
Exploitation context
The bundle does not show CISA KEV listing or evidence of active exploitation. The practical impact is integrity weakening of HTTPS enforcement state, not code execution, credential theft, or denial of service as described in the supplied CVSS vector.
Researcher notes
Do not broaden affected scope beyond curl and named vendor advisories without product evidence. Focus validation on HSTS persistence behavior, version/package provenance, and whether path construction allows excessive file names. Evidence in the bundle is sufficient for risk triage but not full product-specific remediation detail.
Mitigation direction
Update curl using the curl, Debian, Fedora, NetApp, or Siemens guidance that applies to your environment.
Avoid user-controlled or excessively long HSTS file names where curl HSTS persistence is enabled.
Check vendor advisories before declaring remediation complete.
Treat appliances and embedded products separately from operating-system curl packages.
Validation and detection
Inventory curl versions and products that embed curl.
Identify workflows that enable persistent curl HSTS storage.
Review whether HSTS file paths can become excessively long or user influenced.
Confirm vendor advisory status for Debian, Fedora, NetApp, and Siemens assets.
Verify remediated systems no longer run affected curl builds.
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.
cwe · low confidence lookup
CWE-311: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-311 · source CWE mapping
Missing Encryption of Sensitive Data
Missing Encryption of Sensitive Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.