CVE-2025-24002
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 · uneditedAn unauthenticated remote attacker can use MQTT messages to crash a service on charging stations complying with German Calibration Law, resulting in a temporary denial-of-service for these stations until they got restarted by the watchdog.
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 confidenceAn unauthenticated remote attacker can send specially crafted MQTT messages to crash a service on EV charging stations that comply with German Calibration Law. The crash causes temporary denial-of-service until the watchdog mechanism restarts the affected service.
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<= 1.6.5<= 1.6.5<= 1.6.5<= 1.6.5CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 Charx Sec model numberLocate the model label on the charging station physical unit or check the device inventory/documentation. Confirm it is one of: Charx Sec 3000, Charx Sec 3050, Charx Sec 3100, or Charx Sec 3150.Affected if The model is NOT one of these four variants, then the device is not affected by this specific CVE.
-
Check the installed firmware versionAccess the device management interface or use the vendor's diagnostic tool to retrieve the current firmware version. Compare against the affected range: any version <= 1.6.5 is vulnerable.Affected if Firmware version is 1.6.5 or lower, the device falls within the affected version range.
-
Verify the MQTT service is network-accessibleScan the network for open MQTT ports (typically 1883 for unencrypted, 8883 for TLS) on the charging station IP address, or review firewall/network segmentation rules to determine if the MQTT service is exposed to untrusted networks.Affected if MQTT ports are reachable from untrusted or external networks, the device can be attacked remotely.
-
Confirm the service is currently runningCheck the device status via its management interface or query the service health endpoint to see if the EV charging service is in a running state.Affected if The service has crashed and is awaiting watchdog restart, the device is currently experiencing the DoS condition from this vulnerability.
A device is affected if it is a Charx Sec 3000/3050/3100/3150 model running firmware version 1.6.5 or lower with an exposed MQTT service accessible to potential attackers.
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 dataImplement MQTT message validation and authentication, apply network segmentation to restrict MQTT traffic to authorized sources, and apply vendor patches when available.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24002 — 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-2025-24002 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