BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-9681High confidence

HSTS subdomain overwrites parent cache entry

curl · curl

6.5MediumCVSS 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 40 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 3 Nov 2025

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.99% 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 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 40 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, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

8 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.11.0-r0Alpine Security Database ↗Source updated 3 Nov 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.11.0-r0Alpine Security Database ↗Source updated 3 Nov 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.11.0-r0Alpine Security Database ↗Source updated 3 Nov 2026
Debian trixietrixie · sourcecurlVendor fix publishedDebian records a fixed source-package version for this release.8.11.0-1Debian Security Tracker ↗Source updated 4 Nov 2026
Debian bookwormbookworm · sourcecurlVendor fix publishedDebian records a fixed source-package version for this release.7.88.1-10+deb12u9Debian Security Tracker ↗Source updated 4 Nov 2026
Debian forkyforky · sourcecurlVendor fix publishedDebian records a fixed source-package version for this release.8.11.0-1Debian Security Tracker ↗Source updated 4 Nov 2026
Debian sidsid · sourcecurlVendor fix publishedDebian records a fixed source-package version for this release.8.11.0-1Debian Security Tracker ↗Source updated 4 Nov 2026
Ubuntu 24.04 LTSnoble · standard archivecurlVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.8.5.0-2ubuntu10.5Canonical Ubuntu Security ↗Source updated 4 Nov 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.

4 current
CVE-2024-9681 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitycurl: HSTS subdomain overwrites parent cache entry
9 known affected

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

  • curl as a component of Red Hat Enterprise Linux 9
  • curl-minimal as a component of Red Hat Enterprise Linux 9
  • curl.src as a component of Red Hat Enterprise Linux 9
  • libcurl as a component of Red Hat Enterprise Linux 9
  • libcurl-devel as a component of Red Hat Enterprise Linux 9
  • libcurl-minimal as a component of Red Hat Enterprise Linux 9
  • jbcs-httpd24-curl as a component of Red Hat JBoss Core Services
  • openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4
  • openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4
Summary
A vulnerability was found in curl. When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than intended.
Remediation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
CVE-2024-9681 · CSAF 2.0 · revision 57 · interimSUSE Product Security TeamCVE-2024-9681
44 known affected

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

  • curl as component of SUSE Linux Enterprise Desktop 15 SP4
  • SUSE Linux Enterprise Desktop 15 SP4:libcurl4
  • curl as component of SUSE Linux Enterprise Desktop 15 SP5
  • SUSE Linux Enterprise Desktop 15 SP5:libcurl4
  • curl as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • libcurl4 as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • libcurl4-32bit as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • SUSE Linux Enterprise High Performance Computing 15 SP4:libcurl4
  • SUSE Linux Enterprise High Performance Computing 15 SP5:libcurl4
  • SUSE Linux Enterprise Installer Updates 15 SP4:libcurl4
  • SUSE Linux Enterprise Installer Updates 15 SP5:libcurl4
  • curl as component of SUSE Linux Enterprise Server 12 SP5
Summary
When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.) When `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different period of time than what was asked for by the origin server. If `example.com` for example stops supporting HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set) timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-089022 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-089022: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.3
16 known affected

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

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
  • SCALANCE XCH328 (6GK5328-4TS01-2EC2)
  • SCALANCE XCM324 (6GK5324-8TS01-2AC2)
  • SCALANCE XCM328 (6GK5328-4TS01-2AC2)
  • SCALANCE XCM332 (6GK5332-0GA01-2AC2)
  • SCALANCE XRH334 (24 V DC, 8xFO, CC) (6GK5334-2TS01-2ER3)
  • SCALANCE XRM334 (230 V AC, 12xFO) (6GK5334-3TS01-3AR3)
  • SCALANCE XRM334 (230 V AC, 8xFO) (6GK5334-2TS01-3AR3)
  • SCALANCE XRM334 (230V AC, 2x10G, 24xSFP, 8xSFP+) (6GK5334-5TS01-3AR3)
  • SCALANCE XRM334 (24 V DC, 12xFO) (6GK5334-3TS01-2AR3)
  • SCALANCE XRM334 (24 V DC, 8xFO) (6GK5334-2TS01-2AR3)
Summary
When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.) When `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different period of time than what was asked for by the origin server. If `example.com` for example stops supporting HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set) timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended.
Remediation
Update to V3.3 or later version
SSA-355557 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-355557: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.2
3 known affected

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

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.) When `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different period of time than what was asked for by the origin server. If `example.com` for example stops supporting HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set) timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended.
Remediation
Update to V3.2 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-2024-50377

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 40 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

When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.) When `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different period of time than what was asked for by the origin server. If `example.com` for example stops supporting HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set) timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended.

What

When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.) When `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different period of time than what was asked for by the origin server. If `example.com` for example stops supporting HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set) timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended.

Why

The code performs a comparison between two entities, but the comparison examines the wrong factors or characteristics of the entities, which can lead to incorrect results and resultant weaknesses.

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

When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.) When `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different period of time than what was asked for by the origin server. If `example.com` for example stops supporting HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set) timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended.

Why

The code performs a comparison between two entities, but the comparison examines the wrong factors or characteristics of the entities, which can lead to incorrect results and resultant weaknesses.

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 → Comparison Using Wrong Factors → 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-1025 ↗

CWE-1025: Comparison Using Wrong Factors. The code performs a comparison between two entities, but the comparison examines the wrong factors or characteristics of the entities, which can lead to incorrect results and resultant weaknesses.

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:H/A:L

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.IHighIntegrity impact: A successful attack can cause a major loss.ALowAvailability impact: A successful attack can cause a limited 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-1025Public 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-2025-0668Apple macOS: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Apple macOS ausnutzen, um erhöhte Rechte - sogar Root-Rechte - zu erlangen, um vertrauliche Informationen offenzulegen, um beliebigen Code auszuführen, um Daten zu manipulieren, um Sicherheitsmaßnahmen - sogar Sandbox-Einschränkungen - zu umgehen oder um einen Denial-of-Service-Zustand auszulösen.

Official advisory ↗
BSI · German · WID-SEC-2025-0663Apple iOS und iPadOS: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Apple iOS und Apple iPadOS ausnutzen, um vertrauliche Informationen preiszugeben, beliebigen Code auszuführen, einen Denial-of-Service-Zustand herbeizuführen, Sicherheitsmaßnahmen zu umgehen, erhöhte Rechte zu erlangen oder Daten zu manipulieren.

Official advisory ↗
BSI · German · WID-SEC-2024-3342cURL: Schwachstelle ermöglicht Denial of Service

Ein Angreifer kann eine Schwachstelle in cURL ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241113Security Bulletin 13 Nov 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 13 Nov 2024, published on 13 November 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CISA · English · ICSA-26-043-06Siemens SINEC OS

When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.) When `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different period of time than what was asked for by the origin server. If `example.com` for example stops supporting HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set) timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended.

Official advisory ↗
CISA · English · ICSA-25-226-07Siemens Third-Party Components in SINEC OS

When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making it end sooner or later than otherwise intended. This affects curl using applications that enable HSTS and use URLs with the insecure `HTTP://` scheme and perform transfers with hosts like `x.example.com` as well as `example.com` where the first host is a subdomain of the second host. (The HSTS cache either needs to have been populated manually or there needs to have been previous HTTPS accesses done as the cache needs to have entries for the domains involved to trigger this problem.) When `x.example.com` responds with `Strict-Transport-Security:` headers, this bug can make the subdomain's expiry timeout *bleed over* and get set for the parent domain `example.com` in curl's HSTS cache. The result of a triggered bug is that HTTP accesses to `example.com` get converted to HTTPS for a different period of time than what was asked for by the origin server. If `example.com` for example stops supporting HTTPS at its expiry time, curl might then fail to access `http://example.com` until the (wrongly set) timeout expires. This bug can also expire the parent's entry *earlier*, thus making curl inadvertently switch back to insecure HTTP earlier than otherwise intended.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1385Avis du CERT-FR

.cve.org/CVERecord?id=CVE-2024-8638 Référence CVE CVE-2024-8904 https://www.cve.org/CVERecord?id=CVE-2024-8904 Référence CVE CVE-2024-8905 https://www.cve.org/CVERecord?id=CVE-2024-8905 Référence CVE CVE-2024-9042 https://www.cve.org/CVERecord?id=CVE-2024-9042 Référence CVE CVE-2024-9121 https://www.cve.org/CVERecord?id=CVE-2024-9121 Référence CVE CVE-2024-9122 https://www.cve.org/CVERecord?id=CVE-2024-9122 Référence CVE CVE-2024-9287 https://www.cve.org/CVERecord?id=CVE-2024-9287 Référence CVE CVE-2024-9602 https://www.cve.org/CVERecord?id=CVE-2024-9602 Référence CVE CVE-2024-9603 https://www.cve.org/CVERecord?id=CVE-2024-9603 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2024-9859 https://www.cve.org/CVERecord?id=CVE-2024-9859 Référence CVE CVE-2025-0167 https://www.cve.org/CVERecord?id=CVE-2025-0167 Référence CVE CVE-2025-0291 https://www.cve.org/CVERecord?id=CVE-2025-0291 Référence CVE CVE-2025-0306 https://www.cve.org/CVERecord?id=CVE-2025-0306 Référence CVE CVE-2025-0395 https://www.cve.org/CVERecord?id=CVE-2025-0395 Référence CVE CVE-2025-0426 https://www.cve.org/CVERecord?id=CVE-2025-0426 Référence CVE CVE-2025-0434 https://www.cve.org/CVERecord?id=CVE-2025-0434 Référence CVE CVE-2025-0611 https://www.cve.org/CVERecord?id=CVE-2025-0611 Ré

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

rt.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38354 Référence CVE CVE-2024-11053 https://www.cve.org/CVERecord?id=CVE-2024-11053 Référence CVE CVE-2024-31227 https://www.cve.org/CVERecord?id=CVE-2024-31227 Référence CVE CVE-2024-31228 https://www.cve.org/CVERecord?id=CVE-2024-31228 Référence CVE CVE-2024-31449 https://www.cve.org/CVERecord?id=CVE-2024-31449 Référence CVE CVE-2024-46981 https://www.cve.org/CVERecord?id=CVE-2024-46981 Référence CVE CVE-2024-51741 https://www.cve.org/CVERecord?id=CVE-2024-51741 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-13034 https://www.cve.org/CVERecord?id=CVE-2025-13034 Référence CVE CVE-2025-14017 https://www.cve.org/CVERecord?id=CVE-2025-14017 Référence CVE CVE-2025-14524 https://www.cve.org/CVERecord?id=CVE-2025-14524 Référence CVE CVE-2025-15079 https://www.cve.org/CVERecord?id=CVE-2025-15079 Référence CVE CVE-2025-15224 https://www.cve.org/CVERecord?id=CVE-2025-15224 Référence CVE CVE-2025-21605 https://www.cve.org/CVERecord?id=CVE-2025-21605 Référence CVE CVE-2025-27151 https://www.cve.org/CVERecord?id=CVE-2025-27151 Référence CVE CVE-2025-32023 https://www.cve.org/CVERecord?id=C

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

rg/CVERecord?id=CVE-2024-5321 Référence CVE CVE-2024-53899 https://www.cve.org/CVERecord?id=CVE-2024-53899 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=CVE-2024-5535 Référence CVE CVE-2024-55549 https://www.cve.org/CVERecord?id=CVE-2024-55549 Référence CVE CVE-2024-58251 https://www.cve.org/CVERecord?id=CVE-2024-58251 Référence CVE CVE-2024-6345 https://www.cve.org/CVERecord?id=CVE-2024-6345 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-7592 https://www.cve.org/CVERecord?id=CVE-2024-7592 Référence CVE CVE-2024-8775 https://www.cve.org/CVERecord?id=CVE-2024-8775 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-0938 https://www.cve.org/CVERecord?id=CVE-2025-0938 Référence CVE CVE-2025-11143 https://www.cve.org/CVERecord?id=CVE-2025-11143 Référence CVE CVE-2025-11187 https://www.cve.org/CVERecord?id=CVE-2025-11187 Référence CVE CVE-2025-11226 https://www.cve.org/CVERecord?id=CVE-2025-11226 Référence CVE CVE-2025-11468 https://www.cve.org/CVERecord?id=CVE-2025-11468 Référence CVE CVE-2025-12084 https://www.cve.org/CVERecord?id=CVE-2025-12084 Référence CVE CVE-2025-12183 https://www.cve.org/CVERecord?id=CVE-2025-12183 Référence CVE CVE-2025-13151 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0266Multiples vulnérabilités dans VMware Tanzu

Record?id=CVE-2023-4156 Référence CVE CVE-2023-45322 https://www.cve.org/CVERecord?id=CVE-2023-45322 Référence CVE CVE-2023-50495 https://www.cve.org/CVERecord?id=CVE-2023-50495 Référence CVE CVE-2024-0232 https://www.cve.org/CVERecord?id=CVE-2024-0232 Référence CVE CVE-2024-11053 https://www.cve.org/CVERecord?id=CVE-2024-11053 Référence CVE CVE-2024-13176 https://www.cve.org/CVERecord?id=CVE-2024-13176 Référence CVE CVE-2024-34459 https://www.cve.org/CVERecord?id=CVE-2024-34459 Référence CVE CVE-2024-41996 https://www.cve.org/CVERecord?id=CVE-2024-41996 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-13151 https://www.cve.org/CVERecord?id=CVE-2025-13151 Référence CVE CVE-2025-14017 https://www.cve.org/CVERecord?id=CVE-2025-14017 Référence CVE CVE-2025-14087 https://www.cve.org/CVERecord?id=CVE-2025-14087 Référence CVE CVE-2025-14512 https://www.cve.org/CVERecord?id=CVE-2025-14512 Référence CVE CVE-2025-14831 https://www.cve.org/CVERecord?id=CVE-2025-14831 Référence CVE CVE-2025-15281 https://www.cve.org/CVERecord?id=CVE-2025-15281 Référence CVE CVE-2025-1632 https://www.cve.org/CVERecord?id=CVE-2025-1632 Référence CVE CVE-2025-27113 https://www.cve.org/CVERecord?id=CVE

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

.cve.org/CVERecord?id=CVE-2024-6763 Référence CVE CVE-2024-7006 https://www.cve.org/CVERecord?id=CVE-2024-7006 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-8088 https://www.cve.org/CVERecord?id=CVE-2024-8088 Référence CVE CVE-2024-8096 https://www.cve.org/CVERecord?id=CVE-2024-8096 Référence CVE CVE-2024-8176 https://www.cve.org/CVERecord?id=CVE-2024-8176 Référence CVE CVE-2024-8244 https://www.cve.org/CVERecord?id=CVE-2024-8244 Référence CVE CVE-2024-9143 https://www.cve.org/CVERecord?id=CVE-2024-9143 Référence CVE CVE-2024-9287 https://www.cve.org/CVERecord?id=CVE-2024-9287 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-0167 https://www.cve.org/CVERecord?id=CVE-2025-0167 Référence CVE CVE-2025-0395 https://www.cve.org/CVERecord?id=CVE-2025-0395 Référence CVE CVE-2025-0665 https://www.cve.org/CVERecord?id=CVE-2025-0665 Référence CVE CVE-2025-0725 https://www.cve.org/CVERecord?id=CVE-2025-0725 Référence CVE CVE-2025-0840 https://www.cve.org/CVERecord?id=CVE-2025-0840 Référence CVE CVE-2025-0913 https://www.cve.org/CVERecord?id=CVE-2025-0913 Référence CVE CVE-2025-0938 https://www.cve.org/CVERecord?id=CVE-2025-0938 Référence CVE CVE-2025-10148 https://www.cve.org/CVERecord?id=CVE-2025-10148

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

g/CVERecord?id=CVE-2024-56433 Référence CVE CVE-2024-56538 https://www.cve.org/CVERecord?id=CVE-2024-56538 Référence CVE CVE-2024-58011 https://www.cve.org/CVERecord?id=CVE-2024-58011 Référence CVE CVE-2024-58251 https://www.cve.org/CVERecord?id=CVE-2024-58251 Référence CVE CVE-2024-6119 https://www.cve.org/CVERecord?id=CVE-2024-6119 Référence CVE CVE-2024-7254 https://www.cve.org/CVERecord?id=CVE-2024-7254 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-8096 https://www.cve.org/CVERecord?id=CVE-2024-8096 Référence CVE CVE-2024-9143 https://www.cve.org/CVERecord?id=CVE-2024-9143 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-0167 https://www.cve.org/CVERecord?id=CVE-2025-0167 Référence CVE CVE-2025-0725 https://www.cve.org/CVERecord?id=CVE-2025-0725 Référence CVE CVE-2025-0913 https://www.cve.org/CVERecord?id=CVE-2025-0913 Référence CVE CVE-2025-10148 https://www.cve.org/CVERecord?id=CVE-2025-10148 Référence CVE CVE-2025-10543 https://www.cve.org/CVERecord?id=CVE-2025-10543 Référence CVE CVE-2025-10966 https://www.cve.org/CVERecord?id=CVE-2025-10966 Référence CVE CVE-2025-11065 https://www.cve.org/CVERecord?id=CVE-2025-11065 Référence CVE CVE-2025-11187 https://www.cve.org/CVERecord?id=CVE-202

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

g/CVERecord?id=CVE-2024-12718 Référence CVE CVE-2024-41996 https://www.cve.org/CVERecord?id=CVE-2024-41996 Référence CVE CVE-2024-47619 https://www.cve.org/CVERecord?id=CVE-2024-47619 Référence CVE CVE-2024-52533 https://www.cve.org/CVERecord?id=CVE-2024-52533 Référence CVE CVE-2024-6197 https://www.cve.org/CVERecord?id=CVE-2024-6197 Référence CVE CVE-2024-6874 https://www.cve.org/CVERecord?id=CVE-2024-6874 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-8006 https://www.cve.org/CVERecord?id=CVE-2024-8006 Référence CVE CVE-2024-8096 https://www.cve.org/CVERecord?id=CVE-2024-8096 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-0167 https://www.cve.org/CVERecord?id=CVE-2025-0167 Référence CVE CVE-2025-0665 https://www.cve.org/CVERecord?id=CVE-2025-0665 Référence CVE CVE-2025-0725 https://www.cve.org/CVERecord?id=CVE-2025-0725 Référence CVE CVE-2025-10148 https://www.cve.org/CVERecord?id=CVE-2025-10148 Référence CVE CVE-2025-1390 https://www.cve.org/CVERecord?id=CVE-2025-1390 Référence CVE CVE-2025-27587 https://www.cve.org/CVERecord?id=CVE-2025-27587 Référence CVE CVE-2025-32433 https://www.cve.org/CVERecord?id=CVE-2025-32433 Référence CVE CVE-2025-3360 https://www.cve.org/CVERecord?id=CVE-2025-3

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

.cve.org/CVERecord?id=CVE-2024-6232 Référence CVE CVE-2024-6923 https://www.cve.org/CVERecord?id=CVE-2024-6923 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-7592 https://www.cve.org/CVERecord?id=CVE-2024-7592 Référence CVE CVE-2024-8088 https://www.cve.org/CVERecord?id=CVE-2024-8088 Référence CVE CVE-2024-8096 https://www.cve.org/CVERecord?id=CVE-2024-8096 Référence CVE CVE-2024-8176 https://www.cve.org/CVERecord?id=CVE-2024-8176 Référence CVE CVE-2024-9143 https://www.cve.org/CVERecord?id=CVE-2024-9143 Référence CVE CVE-2024-9287 https://www.cve.org/CVERecord?id=CVE-2024-9287 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-0167 https://www.cve.org/CVERecord?id=CVE-2025-0167 Référence CVE CVE-2025-0306 https://www.cve.org/CVERecord?id=CVE-2025-0306 Référence CVE CVE-2025-0725 https://www.cve.org/CVERecord?id=CVE-2025-0725 Référence CVE CVE-2025-0938 https://www.cve.org/CVERecord?id=CVE-2025-0938 Référence CVE CVE-2025-10966 https://www.cve.org/CVERecord?id=CVE-2025-10966 Référence CVE CVE-2025-12817 https://www.cve.org/CVERecord?id=CVE-2025-12817 Référence CVE CVE-2025-12818 https://www.cve.org/CVERecord?id=CVE-2025-12818 Référence CVE CVE-2025-1352 https://www.cve.org/CVERecord?id=CVE-2025-1

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

.cve.org/CVERecord?id=CVE-2024-7254 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-7592 https://www.cve.org/CVERecord?id=CVE-2024-7592 Référence CVE CVE-2024-8088 https://www.cve.org/CVERecord?id=CVE-2024-8088 Référence CVE CVE-2024-8096 https://www.cve.org/CVERecord?id=CVE-2024-8096 Référence CVE CVE-2024-8176 https://www.cve.org/CVERecord?id=CVE-2024-8176 Référence CVE CVE-2024-8508 https://www.cve.org/CVERecord?id=CVE-2024-8508 Référence CVE CVE-2024-9143 https://www.cve.org/CVERecord?id=CVE-2024-9143 Référence CVE CVE-2024-9287 https://www.cve.org/CVERecord?id=CVE-2024-9287 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-0167 https://www.cve.org/CVERecord?id=CVE-2025-0167 Référence CVE CVE-2025-0306 https://www.cve.org/CVERecord?id=CVE-2025-0306 Référence CVE CVE-2025-0395 https://www.cve.org/CVERecord?id=CVE-2025-0395 Référence CVE CVE-2025-0725 https://www.cve.org/CVERecord?id=CVE-2025-0725 Référence CVE CVE-2025-0838 https://www.cve.org/CVERecord?id=CVE-2025-0838 Référence CVE CVE-2025-0913 https://www.cve.org/CVERecord?id=CVE-2025-0913 Référence CVE CVE-2025-0938 https://www.cve.org/CVERecord?id=CVE-2025-0938 Référence CVE CVE-2025-10148 https://www.cve.org/CVERecord?id=CVE-2025-10148

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

.cve.org/CVERecord?id=CVE-2024-7012 Référence CVE CVE-2024-7254 https://www.cve.org/CVERecord?id=CVE-2024-7254 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-7592 https://www.cve.org/CVERecord?id=CVE-2024-7592 Référence CVE CVE-2024-8088 https://www.cve.org/CVERecord?id=CVE-2024-8088 Référence CVE CVE-2024-8096 https://www.cve.org/CVERecord?id=CVE-2024-8096 Référence CVE CVE-2024-8805 https://www.cve.org/CVERecord?id=CVE-2024-8805 Référence CVE CVE-2024-9143 https://www.cve.org/CVERecord?id=CVE-2024-9143 Référence CVE CVE-2024-9287 https://www.cve.org/CVERecord?id=CVE-2024-9287 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-0167 https://www.cve.org/CVERecord?id=CVE-2025-0167 Référence CVE CVE-2025-0237 https://www.cve.org/CVERecord?id=CVE-2025-0237 Référence CVE CVE-2025-0238 https://www.cve.org/CVERecord?id=CVE-2025-0238 Référence CVE CVE-2025-0239 https://www.cve.org/CVERecord?id=CVE-2025-0239 Référence CVE CVE-2025-0240 https://www.cve.org/CVERecord?id=CVE-2025-0240 Référence CVE CVE-2025-0241 https://www.cve.org/CVERecord?id=CVE-2025-0241 Référence CVE CVE-2025-0242 https://www.cve.org/CVERecord?id=CVE-2025-0242 Référence CVE CVE-2025-0243 https://www.cve.org/CVERecord?id=CVE-2025-0243 Ré

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

d?id=CVE-2024-56748 Référence CVE CVE-2024-56754 https://www.cve.org/CVERecord?id=CVE-2024-56754 Référence CVE CVE-2024-56756 https://www.cve.org/CVERecord?id=CVE-2024-56756 Référence CVE CVE-2024-56770 https://www.cve.org/CVERecord?id=CVE-2024-56770 Référence CVE CVE-2024-56779 https://www.cve.org/CVERecord?id=CVE-2024-56779 Référence CVE CVE-2024-56780 https://www.cve.org/CVERecord?id=CVE-2024-56780 Référence CVE CVE-2024-56781 https://www.cve.org/CVERecord?id=CVE-2024-56781 Référence CVE CVE-2024-56785 https://www.cve.org/CVERecord?id=CVE-2024-56785 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-30033 https://www.cve.org/CVERecord?id=CVE-2025-30033 Référence CVE CVE-2025-30034 https://www.cve.org/CVERecord?id=CVE-2025-30034 Référence CVE CVE-2025-40570 https://www.cve.org/CVERecord?id=CVE-2025-40570 Référence CVE CVE-2025-40746 https://www.cve.org/CVERecord?id=CVE-2025-40746 Référence CVE CVE-2025-40751 https://www.cve.org/CVERecord?id=CVE-2025-40751 Référence CVE CVE-2025-40752 https://www.cve.org/CVERecord?id=CVE-2025-40752 Référence CVE CVE-2025-40753 https://www.cve.org/CVERecord?id=CVE-2025-40753 Référence CVE CVE-2025-40759 https://www.cve.org/CVERecord?id=C

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

.cve.org/CVERecord?id=CVE-2024-6232 Référence CVE CVE-2024-6923 https://www.cve.org/CVERecord?id=CVE-2024-6923 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-7592 https://www.cve.org/CVERecord?id=CVE-2024-7592 Référence CVE CVE-2024-8088 https://www.cve.org/CVERecord?id=CVE-2024-8088 Référence CVE CVE-2024-8096 https://www.cve.org/CVERecord?id=CVE-2024-8096 Référence CVE CVE-2024-8805 https://www.cve.org/CVERecord?id=CVE-2024-8805 Référence CVE CVE-2024-9143 https://www.cve.org/CVERecord?id=CVE-2024-9143 Référence CVE CVE-2024-9287 https://www.cve.org/CVERecord?id=CVE-2024-9287 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-0167 https://www.cve.org/CVERecord?id=CVE-2025-0167 Référence CVE CVE-2025-0725 https://www.cve.org/CVERecord?id=CVE-2025-0725 Référence CVE CVE-2025-0913 https://www.cve.org/CVERecord?id=CVE-2025-0913 Référence CVE CVE-2025-0938 https://www.cve.org/CVERecord?id=CVE-2025-0938 Référence CVE CVE-2025-1795 https://www.cve.org/CVERecord?id=CVE-2025-1795 Référence CVE CVE-2025-21502 https://www.cve.org/CVERecord?id=CVE-2025-21502 Référence CVE CVE-2025-21587 https://www.cve.org/CVERecord?id=CVE-2025-21587 Référence CVE CVE-2025-21613 https://www.cve.org/CVERecord?id=CVE-2025-21

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

CVERecord?id=CVE-2024-47875 Référence CVE CVE-2024-48949 https://www.cve.org/CVERecord?id=CVE-2024-48949 Référence CVE CVE-2024-49767 https://www.cve.org/CVERecord?id=CVE-2024-49767 Référence CVE CVE-2024-52616 https://www.cve.org/CVERecord?id=CVE-2024-52616 Référence CVE CVE-2024-52804 https://www.cve.org/CVERecord?id=CVE-2024-52804 Référence CVE CVE-2024-6345 https://www.cve.org/CVERecord?id=CVE-2024-6345 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-8096 https://www.cve.org/CVERecord?id=CVE-2024-8096 Référence CVE CVE-2024-9143 https://www.cve.org/CVERecord?id=CVE-2024-9143 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-0167 https://www.cve.org/CVERecord?id=CVE-2025-0167 Référence CVE CVE-2025-0725 https://www.cve.org/CVERecord?id=CVE-2025-0725 Référence CVE CVE-2025-20300 https://www.cve.org/CVERecord?id=CVE-2025-20300 Référence CVE CVE-2025-20319 https://www.cve.org/CVERecord?id=CVE-2025-20319 Référence CVE CVE-2025-20320 https://www.cve.org/CVERecord?id=CVE-2025-20320 Référence CVE CVE-2025-20321 https://www.cve.org/CVERecord?id=CVE-2025-20321 Référence CVE CVE-2025-20322 https://www.cve.org/CVERecord?id=CVE-2025-20322 Référence CVE CVE-2025-20323 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0448Multiples vulnérabilités dans Tenable Nessus Network Monitor

De multiples vulnérabilités ont été découvertes dans Tenable Nessus Network Monitor. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une élévation de privilèges et un déni de service à distance.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0328Multiples vulnérabilités dans Tenable Security Center

De multiples vulnérabilités ont été découvertes dans Tenable Security Center. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

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

d?id=CVE-2023-27043 Référence CVE CVE-2024-40864 https://www.cve.org/CVERecord?id=CVE-2024-40864 Référence CVE CVE-2024-48958 https://www.cve.org/CVERecord?id=CVE-2024-48958 Référence CVE CVE-2024-54502 https://www.cve.org/CVERecord?id=CVE-2024-54502 Référence CVE CVE-2024-54508 https://www.cve.org/CVERecord?id=CVE-2024-54508 Référence CVE CVE-2024-54533 https://www.cve.org/CVERecord?id=CVE-2024-54533 Référence CVE CVE-2024-54534 https://www.cve.org/CVERecord?id=CVE-2024-54534 Référence CVE CVE-2024-54543 https://www.cve.org/CVERecord?id=CVE-2024-54543 Référence CVE CVE-2024-56171 https://www.cve.org/CVERecord?id=CVE-2024-56171 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-24085 https://www.cve.org/CVERecord?id=CVE-2025-24085 Référence CVE CVE-2025-24093 https://www.cve.org/CVERecord?id=CVE-2025-24093 Référence CVE CVE-2025-24095 https://www.cve.org/CVERecord?id=CVE-2025-24095 Référence CVE CVE-2025-24097 https://www.cve.org/CVERecord?id=CVE-2025-24097 Référence CVE CVE-2025-24113 https://www.cve.org/CVERecord?id=CVE-2025-24113 Référence CVE CVE-2025-24126 https://www.cve.org/CVERecord?id=CVE-2025-24126 Référence CVE CVE-2025-24129 https://www.cve.org/CVERecord?id=CVE-2025-24129 Référence CVE CVE-2025-24131 https://www.cve.org/CVERecord?id=C

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

ecord?id=CVE-2024-27270 Référence CVE CVE-2024-29857 https://www.cve.org/CVERecord?id=CVE-2024-29857 Référence CVE CVE-2024-30171 https://www.cve.org/CVERecord?id=CVE-2024-30171 Référence CVE CVE-2024-30172 https://www.cve.org/CVERecord?id=CVE-2024-30172 Référence CVE CVE-2024-41783 https://www.cve.org/CVERecord?id=CVE-2024-41783 Référence CVE CVE-2024-45296 https://www.cve.org/CVERecord?id=CVE-2024-45296 Référence CVE CVE-2024-51462 https://www.cve.org/CVERecord?id=CVE-2024-51462 Référence CVE CVE-2024-7348 https://www.cve.org/CVERecord?id=CVE-2024-7348 Référence CVE CVE-2024-8096 https://www.cve.org/CVERecord?id=CVE-2024-8096 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Gestion détaillée du document le 15 novembre 2024 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.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-013466Haxx の cURL における不適切な比較に関する脆弱性

Haxx の cURL には、不適切な比較に関する脆弱性が存在します。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2025-0103Kwetsbaarheden verholpen in Apple iOS en iPadOS

De kwetsbaarheden omvatten onder andere geheugenbeheerproblemen, ongeautoriseerde toegang tot gevoelige gebruikersdata, en de mogelijkheid voor applicaties om hun sandbox-omgevingen te ontsnappen. Deze kwetsbaarheden konden leiden tot ongeautoriseerde toegang, gegevenswijzigingen, of zelfs Denial-of-Service. Voor succesvol misbruik moet de kwaadwillende het slachtoffer misleiden een malafide app te installeren of link te volgen.

Official advisory ↗
NCSC-NL · Dutch · NCSC-2025-0102Kwetsbaarheden verholpen in Apple macOS

De kwetsbaarheden omvatten onder andere problemen met ongeautoriseerde toegang tot gevoelige gebruikersdata, logboekregistratie-issues, en kwetsbaarheden die het mogelijk maakten voor applicaties om root-rechten te verkrijgen. Deze kwetsbaarheden konden worden misbruikt door kwaadwillenden om toegang te krijgen tot gevoelige informatie of om systeeminstabiliteit te veroorzaken.

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
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
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
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Official vendor articles8 stored documents

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

  • About the security content of iPadOS 17.7.6 - Apple Support →Original publisher ↗Searchable text snapshot · Captured 21 Oct 2026Apple Store Mac iPad iPhone Watch Vision AirPods Home Entertainment Accessories Support 0 + "},{"name":"compact","assetInline":" "}],"analyticsAttributes":[{"name":"data-analytics-title","value":"apple home"}]},{"id":"ad4a2a26eb4836393385e9f6c61b526b4a3cb31409c5ed8730ce7a704dd7132f","name":"store","text":"
  • About the security content of watchOS 11.4 - Apple Support →Original publisher ↗Searchable text snapshot · Captured 19 Oct 2026Apple Store Mac iPad iPhone Watch Vision AirPods Home Entertainment Accessories Support 0 + "},{"name":"compact","assetInline":" "}],"analyticsAttributes":[{"name":"data-analytics-title","value":"apple home"}]},{"id":"ad4a2a26eb4836393385e9f6c61b526b4a3cb31409c5ed8730ce7a704dd7132f","name":"store","text":"
  • About the security content of tvOS 18.4 - Apple Support →Original publisher ↗Searchable text snapshot · Captured 19 Oct 2026Apple Store Mac iPad iPhone Watch Vision AirPods Home Entertainment Accessories Support 0 + "},{"name":"compact","assetInline":" "}],"analyticsAttributes":[{"name":"data-analytics-title","value":"apple home"}]},{"id":"ad4a2a26eb4836393385e9f6c61b526b4a3cb31409c5ed8730ce7a704dd7132f","name":"store","text":"
  • About the security content of visionOS 2.4 - Apple Support →Original publisher ↗Searchable text snapshot · Captured 19 Oct 2026Apple Store Mac iPad iPhone Watch Vision AirPods Home Entertainment Accessories Support 0 + "},{"name":"compact","assetInline":" "}],"analyticsAttributes":[{"name":"data-analytics-title","value":"apple home"}]},{"id":"ad4a2a26eb4836393385e9f6c61b526b4a3cb31409c5ed8730ce7a704dd7132f","name":"store","text":"
  • About the security content of macOS Sonoma 14.7.5 - Apple Support →Original publisher ↗Searchable text snapshot · Captured 29 Sep 2026Apple Store Mac iPad iPhone Watch Vision AirPods TV & Home Entertainment Accessories Support 0 + "},{"name":"compact","assetInline":" "}],"analyticsAttributes":[{"name":"data-analytics-title","value":"apple home"}]},{"id":"ad4a2a26eb4836393385e9f6c61b526b4a3cb31409c5ed8730ce7a704dd7132f","name":"store","te
  • About the security content of macOS Ventura 13.7.5 - Apple Support →Original publisher ↗Searchable text snapshot · Captured 29 Sep 2026Apple Store Mac iPad iPhone Watch Vision AirPods TV & Home Entertainment Accessories Support 0 + "},{"name":"compact","assetInline":" "}],"analyticsAttributes":[{"name":"data-analytics-title","value":"apple home"}]},{"id":"ad4a2a26eb4836393385e9f6c61b526b4a3cb31409c5ed8730ce7a704dd7132f","name":"store","te
  • About the security content of macOS Sequoia 15.4 - Apple Support →Original publisher ↗Searchable text snapshot · Captured 28 Sep 2026Apple Store Mac iPad iPhone Watch Vision AirPods TV & Home Entertainment Accessories Support 0 + "},{"name":"compact","assetInline":" "}],"analyticsAttributes":[{"name":"data-analytics-title","value":"apple home"}]},{"id":"ad4a2a26eb4836393385e9f6c61b526b4a3cb31409c5ed8730ce7a704dd7132f","name":"store","te
  • About the security content of iOS 18.4 and iPadOS 18.4 - Apple Support →Original publisher ↗Searchable text snapshot · Captured 28 Sep 2026Apple Store Mac iPad iPhone Watch Vision AirPods TV & Home Entertainment Accessories Support 0 + "},{"name":"compact","assetInline":" "}],"analyticsAttributes":[{"name":"data-analytics-title","value":"apple home"}]},{"id":"ad4a2a26eb4836393385e9f6c61b526b4a3cb31409c5ed8730ce7a704dd7132f","name":"store","te
04

Evidence and provenance

Published 6 Nov 2024 · Last source change 3 Nov 2025, 20:56 UTC · CWE-1025 · Comparison Using Wrong Factors

CVE recordCVE.org · 5.2
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-2024-50377
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

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-2024-9681 · cve.blacktree.nl