CVE-2024-7392VulnerabilityPublished 22 Nov 2024Updated 25 Nov 2024

CVE-2024-7392: ChargePoint Home Flex · Insufficient Resource Pool

Affects ChargePoint Home FlexSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
ChargePoint Home Flex	Affected =5.5.3.13	Fixed in–

AI-suggested

To mitigate CVE-2024-7392, organizations should implement the following specific measures: 1) Monitor ChargePoint vendor communications closely for firmware updates or patches addressing this vulnerability and apply them promptly once available. 2) Restrict physical and wireless access to the BLE interface of ChargePoint Home Flex devices by deploying them in controlled environments or using physical enclosures to limit attacker proximity. 3) Employ Bluetooth signal jamming or filtering technologies where feasible to reduce unauthorized BLE connection attempts in sensitive locations. 4) Network segmentation and monitoring should be used to detect anomalous BLE connection patterns indicative of exploitation attempts. 5) Consider disabling BLE connectivity if it is not essential for operations or replace it with more secure management interfaces. 6) Educate operational staff about the risks of BLE-based attacks and establish incident response procedures for suspected denial-of-service events affecting EV chargers. These targeted controls go beyond generic advice by focusing on the BLE attack vector and operational context of EV charging infrastructure.

Description

ChargePoint Home Flex Bluetooth Low Energy Denial-of-Service Vulnerability. This vulnerability allows network-adjacent attackers to create a denial-of-service condition on affected installations of ChargePoint Home Flex charging devices. Authentication is not required to exploit this vulnerability. The specific flaw exists within the connection handling of the Bluetooth Low Energy interface. The issue results from limiting the number of active connections to the product. An attacker can leverage this vulnerability to create a denial-of-service condition on the system. Was ZDI-CAN-21455.

Impact

The primary impact of CVE-2024-7392 is a denial-of-service condition on ChargePoint Home Flex devices, which can disrupt the availability of BLE connectivity used for device management, monitoring, or user interaction. While this does not compromise confidentiality or integrity, it can prevent legitimate users or backend systems from connecting to the charger via BLE, potentially causing operational delays or failures in charging sessions. For organizations operating fleets of EV chargers or public charging stations, this could translate into customer dissatisfaction, operational inefficiencies, and reputational damage. In critical infrastructure or commercial settings relying on these chargers, availability loss could have cascading effects on EV fleet readiness or energy management. The ease of exploitation without authentication and user interaction increases the risk of opportunistic attacks, especially in densely populated or publicly accessible charging locations. However, the lack of known exploits and the medium severity score indicate a moderate risk level at present.

CWE-410Insufficient Resource Pool (opens in a new tab)
Class weakness
The product's resource pool is not large enough to handle peak demand, which allows an attacker to prevent others from accessing the resource by using a (relatively) large number of requests for resources.
Architecture and Design
Do not perform resource-intensive transactions for unauthenticated users and/or invalid requests.
Architecture and Design
Consider implementing a velocity check mechanism which would detect abusive behavior.
Operation
Consider load balancing as an option to handle heavy loads.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

zerodayinitiative.com/advisories/ZDI-24-1047/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 03:37 UTC

WeaknessesCWE-410

Technical details

References

Community reviews

Related threats