CVE-2024-23920
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 · uneditedThis vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of ChargePoint Home Flex charging stations. Authentication is not required to exploit this vulnerability. The specific flaw exists within the onboardee module. The issue results from improper access control. An attacker can leverage this vulnerability to execute code in the context of root.
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 · moderate confidenceThis vulnerability in the ChargePoint Home Flex charging station's onboardee module allows unauthenticated network-adjacent attackers to execute arbitrary code with root privileges due to improper access control. The attacker only needs to be on the same network as the device—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 dataall versionsall versionsall versionsCVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 charging station and verify it is a ChargePoint Home Flex model - specifically the Nema 14-50 Plug, Nema 6-50 Plug, or Hardwired variants. Check the physical device label or the ChargePoint app for model information.Affected if The device is any ChargePoint Home Flex variant (Nema 14-50, Nema 6-50, or Hardwired)
-
Determine firmware versionAccess the ChargePoint mobile app or the device's web interface and record the firmware version number displayed in the device settings or status screen.Affected if All firmware versions are affected - any version found indicates the device is vulnerable
-
Check network exposureExamine network configuration to determine if the charging station is accessible from network segments that contain untrusted or guest devices. Review firewall rules and VLAN assignments to identify if the device's management interfaces are reachable from outside the trusted network.Affected if The device is reachable from untrusted network segments without firewall filtering
-
Verify onboardee module accessibilityAttempt to access the device's onboardee service by contacting its IP address on common service ports (typically HTTP/HTTPS on ports 80/443). Determine if the service responds without requiring authentication credentials.Affected if The onboardee module responds to network requests without prompting for authentication
-
Confirm root access exposureReview network logs or perform a test connection to verify that unauthenticated network requests can reach the device's internal services. Check if the device accepts commands without any credential validation.Affected if Unauthenticated network access to the device is possible - no login or credentials are required to communicate with the device's internal services
If the device is a ChargePoint Home Flex (any variant, any firmware version) and its onboardee module is accessible from an untrusted network without authentication, the environment is affected by CVE-2024-23920.
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 dataSegment the charging station network and restrict access via firewall rules until a vendor firmware patch is available; apply firmware updates promptly when released.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23920 — 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-23920 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