BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2023
CVE-2023-27537High confidence

A double free vulnerability exists in libcurl <8.0.0 when sharing HSTS data between separate "handles"

Unknown · https://github.com/curl/curl

Official source article: Siemens SSA-398330 ↗. Check the applicable product and release in the original source.

5.9MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 6 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:High, raised one band.upgradedsince 2 Aug 2024

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 1.86% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown https://github.com/curl/curl and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 6 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · maincurlVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.8.0.0-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · maincurlVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.8.0.0-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · maincurlVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.8.0.0-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcecurlVendor fix publishedDebian records a fixed source-package version for this release.7.88.1-7Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcecurlVendor fix publishedDebian records a fixed source-package version for this release.7.88.1-7Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcecurlVendor fix publishedDebian records a fixed source-package version for this release.7.88.1-7Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcecurlVendor fix publishedDebian records a fixed source-package version for this release.7.88.1-7Debian Security Tracker ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
SSA-398330 · CSAF 2.0 · revision 18 · interimSiemens ProductCERTSSA-398330: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP >= V3.1.0 and < V3.1.5
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)
Summary
A double free vulnerability exists in libcurl <8.0.0 when sharing HSTS data between separate "handles". This sharing was introduced without considerations for do this sharing across separate threads but there was no indication of this fact in the documentation. Due to missing mutexes or thread locks, two threads sharing the same HSTS data could end up doing a double-free or use-after-free.
Remediation
Update to V3.1.5 or later version
SSA-943925 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-943925: Multiple Vulnerabilities in SINEC NMS before V2.0 SP1
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SINEC NMS
Summary
A double free vulnerability exists in libcurl <8.0.0 when sharing HSTS data between separate "handles". This sharing was introduced without considerations for do this sharing across separate threads but there was no indication of this fact in the documentation. Due to missing mutexes or thread locks, two threads sharing the same HSTS data could end up doing a double-free or use-after-free.
Remediation
Update to V2.0 SP1 or later version
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2023-31292

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 6 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

A double free vulnerability exists in libcurl <8.0.0 when sharing HSTS data between separate "handles". This sharing was introduced without considerations for do this sharing across separate threads but there was no indication of this fact in the documentation. Due to missing mutexes or thread locks, two threads sharing the same HSTS data could end up doing a double-free or use-after-free.

What

A double free vulnerability exists in libcurl <8.0.0 when sharing HSTS data between separate "handles". This sharing was introduced without considerations for do this sharing across separate threads but there was no indication of this fact in the documentation. Due to missing mutexes or thread locks, two threads sharing the same HSTS data could end up doing a double-free or use-after-free.

Why

The product calls free() twice on the same memory address.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

A double free vulnerability exists in libcurl <8.0.0 when sharing HSTS data between separate "handles". This sharing was introduced without considerations for do this sharing across separate threads but there was no indication of this fact in the documentation. Due to missing mutexes or thread locks, two threads sharing the same HSTS data could end up doing a double-free or use-after-free.

Why

The product calls free() twice on the same memory address.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Double Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-415 ↗

CWE-415: Double Free. The product calls free() twice on the same memory address.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-415Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2023-2229Splunk Splunk Enterprise: Mehrere Schwachstellen

Ein entfernter, authentifizierter Angreifer kann mehrere Schwachstellen in Splunk Splunk Enterprise ausnutzen, um beliebigen Code auszuführen, einen 'Denial of Service'-Zustand zu verursachen, seine Privilegien zu erweitern und weitere, nicht spezifizierte Auswirkungen zu verursachen.

Official advisory ↗
BSI · German · WID-SEC-2023-1350Splunk Splunk Enterprise: Mehrere Schwachstellen in Komponenten von Drittanbietern

Ein Angreifer kann mehrere Schwachstellen in Splunk Splunk Enterprise in diversen Komponenten von Drittanbietern ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2023-0690cURL: Mehrere Schwachstellen

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in cURL ausnutzen, um Informationen offenzulegen, Sicherheitsvorkehrungen zu umgehen oder unbekannte Auswirkungen zu verursachen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20230405Security Bulletin 05 Apr 2023

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 05 Apr 2023, published on 5 April 2023. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2023-26785 Référence CVE CVE-2023-26965 https://www.cve.org/CVERecord?id=CVE-2023-26965 Référence CVE CVE-2023-27043 https://www.cve.org/CVERecord?id=CVE-2023-27043 Référence CVE CVE-2023-27102 https://www.cve.org/CVERecord?id=CVE-2023-27102 Référence CVE CVE-2023-2731 https://www.cve.org/CVERecord?id=CVE-2023-2731 Référence CVE CVE-2023-27533 https://www.cve.org/CVERecord?id=CVE-2023-27533 Référence CVE CVE-2023-27534 https://www.cve.org/CVERecord?id=CVE-2023-27534 Référence CVE CVE-2023-27535 https://www.cve.org/CVERecord?id=CVE-2023-27535 Référence CVE CVE-2023-27536 https://www.cve.org/CVERecord?id=CVE-2023-27536 Référence CVE CVE-2023-27537 https://www.cve.org/CVERecord?id=CVE-2023-27537 Référence CVE CVE-2023-27538 https://www.cve.org/CVERecord?id=CVE-2023-27538 Référence CVE CVE-2023-2804 https://www.cve.org/CVERecord?id=CVE-2023-2804 Référence CVE CVE-2023-28120 https://www.cve.org/CVERecord?id=CVE-2023-28120 Référence CVE CVE-2023-28154 https://www.cve.org/CVERecord?id=CVE-2023-28154 Référence CVE CVE-2023-28319 https://www.cve.org/CVERecord?id=CVE-2023-28319 Référence CVE CVE-2023-28320 https://www.cve.org/CVERecord?id=CVE-2023-28320 Référence CVE CVE-2023-28321 https://www.cve.org/CVERecord?id=CVE-2023-28321 Référence CVE CVE-2023-28322 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0756Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2023-22097 Référence CVE CVE-2023-22103 https://www.cve.org/CVERecord?id=CVE-2023-22103 Référence CVE CVE-2023-22114 https://www.cve.org/CVERecord?id=CVE-2023-22114 Référence CVE CVE-2023-24329 https://www.cve.org/CVERecord?id=CVE-2023-24329 Référence CVE CVE-2023-2602 https://www.cve.org/CVERecord?id=CVE-2023-2602 Référence CVE CVE-2023-2603 https://www.cve.org/CVERecord?id=CVE-2023-2603 Référence CVE CVE-2023-27043 https://www.cve.org/CVERecord?id=CVE-2023-27043 Référence CVE CVE-2023-27535 https://www.cve.org/CVERecord?id=CVE-2023-27535 Référence CVE CVE-2023-27536 https://www.cve.org/CVERecord?id=CVE-2023-27536 Référence CVE CVE-2023-27537 https://www.cve.org/CVERecord?id=CVE-2023-27537 Référence CVE CVE-2023-27538 https://www.cve.org/CVERecord?id=CVE-2023-27538 Référence CVE CVE-2023-28320 https://www.cve.org/CVERecord?id=CVE-2023-28320 Référence CVE CVE-2023-28321 https://www.cve.org/CVERecord?id=CVE-2023-28321 Référence CVE CVE-2023-28322 https://www.cve.org/CVERecord?id=CVE-2023-28322 Référence CVE CVE-2023-28484 https://www.cve.org/CVERecord?id=CVE-2023-28484 Référence CVE CVE-2023-29383 https://www.cve.org/CVERecord?id=CVE-2023-29383 Référence CVE CVE-2023-29469 https://www.cve.org/CVERecord?id=CVE-2023-29469 Référence CVE CVE-2023-3138 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0119Multiples vulnérabilités dans les produits Siemens

ord?id=CVE-2023-25727 Référence CVE CVE-2023-26081 https://www.cve.org/CVERecord?id=CVE-2023-26081 Référence CVE CVE-2023-2650 https://www.cve.org/CVERecord?id=CVE-2023-2650 Référence CVE CVE-2023-26965 https://www.cve.org/CVERecord?id=CVE-2023-26965 Référence CVE CVE-2023-27522 https://www.cve.org/CVERecord?id=CVE-2023-27522 Référence CVE CVE-2023-27533 https://www.cve.org/CVERecord?id=CVE-2023-27533 Référence CVE CVE-2023-27534 https://www.cve.org/CVERecord?id=CVE-2023-27534 Référence CVE CVE-2023-27535 https://www.cve.org/CVERecord?id=CVE-2023-27535 Référence CVE CVE-2023-27536 https://www.cve.org/CVERecord?id=CVE-2023-27536 Référence CVE CVE-2023-27537 https://www.cve.org/CVERecord?id=CVE-2023-27537 Référence CVE CVE-2023-27538 https://www.cve.org/CVERecord?id=CVE-2023-27538 Référence CVE CVE-2023-28319 https://www.cve.org/CVERecord?id=CVE-2023-28319 Référence CVE CVE-2023-28320 https://www.cve.org/CVERecord?id=CVE-2023-28320 Référence CVE CVE-2023-28321 https://www.cve.org/CVERecord?id=CVE-2023-28321 Référence CVE CVE-2023-28322 https://www.cve.org/CVERecord?id=CVE-2023-28322 Référence CVE CVE-2023-28450 https://www.cve.org/CVERecord?id=CVE-2023-28450 Référence CVE CVE-2023-28466 https://www.cve.org/CVERecord?id=CVE-2023-28466 Référence CVE CVE-2023-28486 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-1015Multiples vulnérabilités dans les produits Siemens

ord?id=CVE-2023-25136 Référence CVE CVE-2023-25139 https://www.cve.org/CVERecord?id=CVE-2023-25139 Référence CVE CVE-2023-2650 https://www.cve.org/CVERecord?id=CVE-2023-2650 Référence CVE CVE-2023-26604 https://www.cve.org/CVERecord?id=CVE-2023-26604 Référence CVE CVE-2023-27371 https://www.cve.org/CVERecord?id=CVE-2023-27371 Référence CVE CVE-2023-27533 https://www.cve.org/CVERecord?id=CVE-2023-27533 Référence CVE CVE-2023-27534 https://www.cve.org/CVERecord?id=CVE-2023-27534 Référence CVE CVE-2023-27535 https://www.cve.org/CVERecord?id=CVE-2023-27535 Référence CVE CVE-2023-27536 https://www.cve.org/CVERecord?id=CVE-2023-27536 Référence CVE CVE-2023-27537 https://www.cve.org/CVERecord?id=CVE-2023-27537 Référence CVE CVE-2023-27538 https://www.cve.org/CVERecord?id=CVE-2023-27538 Référence CVE CVE-2023-28484 https://www.cve.org/CVERecord?id=CVE-2023-28484 Référence CVE CVE-2023-28531 https://www.cve.org/CVERecord?id=CVE-2023-28531 Référence CVE CVE-2023-28831 https://www.cve.org/CVERecord?id=CVE-2023-28831 Référence CVE CVE-2023-29383 https://www.cve.org/CVERecord?id=CVE-2023-29383 Référence CVE CVE-2023-29469 https://www.cve.org/CVERecord?id=CVE-2023-29469 Référence CVE CVE-2023-29491 https://www.cve.org/CVERecord?id=CVE-2023-29491 Référence CVE CVE-2023-29499 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0926Multiples vulnérabilités dans IBM

De multiples vulnérabilités ont été découvertes dans les produits IBM . Certaines d'entre elles permettent à un attaquant de provoquer une élévation de privilèges, une exécution de code arbitraire à distance et une atteinte à la confidentialité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0791Multiples vulnérabilités dans les produits IBM

De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur, une exécution de code arbitraire à distance et un déni de service à distance.

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0701Multiples vulnérabilités dans Splunk

d?id=CVE-2023-23914 Référence CVE CVE-2023-23915 https://www.cve.org/CVERecord?id=CVE-2023-23915 Référence CVE CVE-2023-23916 https://www.cve.org/CVERecord?id=CVE-2023-23916 Référence CVE CVE-2023-24539 https://www.cve.org/CVERecord?id=CVE-2023-24539 Référence CVE CVE-2023-24540 https://www.cve.org/CVERecord?id=CVE-2023-24540 Référence CVE CVE-2023-27533 https://www.cve.org/CVERecord?id=CVE-2023-27533 Référence CVE CVE-2023-27534 https://www.cve.org/CVERecord?id=CVE-2023-27534 Référence CVE CVE-2023-27535 https://www.cve.org/CVERecord?id=CVE-2023-27535 Référence CVE CVE-2023-27536 https://www.cve.org/CVERecord?id=CVE-2023-27536 Référence CVE CVE-2023-27537 https://www.cve.org/CVERecord?id=CVE-2023-27537 Référence CVE CVE-2023-27538 https://www.cve.org/CVERecord?id=CVE-2023-27538 Référence CVE CVE-2023-29400 https://www.cve.org/CVERecord?id=CVE-2023-29400 Référence CVE CVE-2023-29402 https://www.cve.org/CVERecord?id=CVE-2023-29402 Référence CVE CVE-2023-29403 https://www.cve.org/CVERecord?id=CVE-2023-29403 Référence CVE CVE-2023-29404 https://www.cve.org/CVERecord?id=CVE-2023-29404 Référence CVE CVE-2023-29405 https://www.cve.org/CVERecord?id=CVE-2023-29405 Référence CVE CVE-2023-2976 https://www.cve.org/CVERecord?id=CVE-2023-2976 Référence CVE CVE-2023-40592 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0446Multiples vulnérabilités dans les produits IBM

De multiples vulnérabilités ont été découvertes dans les produits IBM . Certaines d'entre elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données, une exécution de code arbitraire à distance et un contournement de la politique de sécurité.

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0444Multiples vulnérabilités dans les produits IBM

d?id=CVE-2023-23916 Référence CVE CVE-2023-24998 https://www.cve.org/CVERecord?id=CVE-2023-24998 Référence CVE CVE-2023-25930 https://www.cve.org/CVERecord?id=CVE-2023-25930 Référence CVE CVE-2023-26021 https://www.cve.org/CVERecord?id=CVE-2023-26021 Référence CVE CVE-2023-26022 https://www.cve.org/CVERecord?id=CVE-2023-26022 Référence CVE CVE-2023-27533 https://www.cve.org/CVERecord?id=CVE-2023-27533 Référence CVE CVE-2023-27534 https://www.cve.org/CVERecord?id=CVE-2023-27534 Référence CVE CVE-2023-27535 https://www.cve.org/CVERecord?id=CVE-2023-27535 Référence CVE CVE-2023-27536 https://www.cve.org/CVERecord?id=CVE-2023-27536 Référence CVE CVE-2023-27537 https://www.cve.org/CVERecord?id=CVE-2023-27537 Référence CVE CVE-2023-27538 https://www.cve.org/CVERecord?id=CVE-2023-27538 Référence CVE CVE-2023-27555 https://www.cve.org/CVERecord?id=CVE-2023-27555 Référence CVE CVE-2023-27559 https://www.cve.org/CVERecord?id=CVE-2023-27559 Référence CVE CVE-2023-29255 https://www.cve.org/CVERecord?id=CVE-2023-29255 Référence CVE CVE-2023-29257 https://www.cve.org/CVERecord?id=CVE-2023-29257 Gestion détaillée du document le 08 juin 2023 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.f

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0428Multiples vulnérabilités dans les produits Splunk

cord?id=CVE-2023-0286 Référence CVE CVE-2023-1370 https://www.cve.org/CVERecord?id=CVE-2023-1370 Référence CVE CVE-2023-23914 https://www.cve.org/CVERecord?id=CVE-2023-23914 Référence CVE CVE-2023-23915 https://www.cve.org/CVERecord?id=CVE-2023-23915 Référence CVE CVE-2023-23916 https://www.cve.org/CVERecord?id=CVE-2023-23916 Référence CVE CVE-2023-27533 https://www.cve.org/CVERecord?id=CVE-2023-27533 Référence CVE CVE-2023-27534 https://www.cve.org/CVERecord?id=CVE-2023-27534 Référence CVE CVE-2023-27535 https://www.cve.org/CVERecord?id=CVE-2023-27535 Référence CVE CVE-2023-27536 https://www.cve.org/CVERecord?id=CVE-2023-27536 Référence CVE CVE-2023-27537 https://www.cve.org/CVERecord?id=CVE-2023-27537 Référence CVE CVE-2023-27538 https://www.cve.org/CVERecord?id=CVE-2023-27538 Référence CVE CVE-2023-32706 https://www.cve.org/CVERecord?id=CVE-2023-32706 Référence CVE CVE-2023-32707 https://www.cve.org/CVERecord?id=CVE-2023-32707 Référence CVE CVE-2023-32708 https://www.cve.org/CVERecord?id=CVE-2023-32708 Référence CVE CVE-2023-32709 https://www.cve.org/CVERecord?id=CVE-2023-32709 Référence CVE CVE-2023-32710 https://www.cve.org/CVERecord?id=CVE-2023-32710 Référence CVE CVE-2023-32711 https://www.cve.org/CVERecord?id=CVE-2023-32711 Référence CVE CVE-2023-32712 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-006572Haxx の libcurl 他複数ベンダの製品における二重解放に関する脆弱性

Haxx の libcurl 他複数ベンダの製品には、二重解放に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Update to V3.1.5 or later version
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 30 Mar 2023 · Last source change 2 Aug 2024, 12:16 UTC · CWE-415 · Double Free

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-31292
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCNA
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    Fixed in 8.0.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    Fixed in 8.0.0 · Fixed: Update to V3.1.5 or later version
    Siemens ProductCERT ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Siemens ProductCERT ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-27537 · cve.blacktree.nl