CVE-2024-7392
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedChargePoint 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe ChargePoint Home Flex EV charger has a vulnerability in its Bluetooth Low Energy interface where the device limits the number of active BLE connections. An attacker within BLE range can exhaust available connection slots by initiating multiple connections, preventing legitimate users from connecting and creating a denial-of-service condition. No authentication is required.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 5.5.3.13CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLocate the physical ChargePoint Home Flex charger and verify it is the Home Flex model. This can also be confirmed through the ChargePoint app under Device Settings or by checking the device label.Affected if The device is not a ChargePoint Home Flex charger, then this specific CVE does not apply.
-
Check the installed firmware versionOpen the ChargePoint mobile app, select the Home Flex device, and navigate to Settings > Device Info to view the firmware version. Alternatively, check the device label or use BLE tooling to query the firmware if available.Affected if The firmware version is exactly 5.5.3.13, then the device is affected by this vulnerability.
-
Verify BLE interface is enabledAttempt to scan for the charger using a BLE scanner app or tool (such as nRF Connect) from a mobile device. The device will appear as 'ChargePoint' with its serial number if BLE is active.Affected if BLE is discoverable and active, the device is vulnerable to connection exhaustion attacks. If BLE is disabled or not discoverable, the attack surface may be reduced.
-
Check for connection availabilityUse a BLE tool to attempt multiple connections to the device. Observe whether the device accepts new connections or returns an error indicating connection slots are exhausted.Affected if The device accepts connections but has a low limit (typically 2-4 concurrent connections), confirming the vulnerability condition exists.
If the device is a ChargePoint Home Flex with firmware version 5.5.3.13 and BLE is enabled, it is affected by this BLE connection exhaustion vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-supplied firmware update when available. If no update exists, consider network segmentation and physical access controls to limit proximity of unauthorized attackers to the BLE interface.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7392 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-7392 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data