CVE-2024-25998
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 perform a command injection in the OCPP Service with limited privileges due to improper input validation.
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 confidenceCommand injection vulnerability in the OCPP (Open Charge Point Protocol) Service allowing unauthenticated remote attackers to execute arbitrary system commands due to improper input validation on user-controlled inputs.
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.5.1< 1.5.1< 1.5.1< 1.5.1CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 modelLocate the device label or access the device management interface to confirm the model is one of: Charx Sec 3000, 3050, 3100, or 3150Affected if The device is any of these four models
-
Check the installed firmware versionAccess the device admin interface or check via firmware version command to determine the current firmware versionAffected if The firmware version is below 1.5.1 (for example, 1.4.x, 1.0.x, etc.)
-
Verify the OCPP service is enabledCheck the device configuration or running services to confirm the OCPP (Open Charge Point Protocol) service is activeAffected if OCPP service is running and accepting connections
-
Determine if OCPP interface is network-accessibleReview network configuration, firewall rules, or port status to check if the OCPP service port is exposed to networkAffected if The OCPP service port is reachable from untrusted networks without authentication barriers
-
Inspect OCPP configuration for input handlingExamine the OCPP service configuration files or settings to verify if user-supplied parameters are processed without proper validationAffected if OCPP accepts user input without documented input validation controls in place
A user is affected if they have a Charx Sec 3000/3050/3100/3150 device running firmware below version 1.5.1 with the OCPP service enabled and accessible.
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.
dbcve · scoped1.5.1
Implement strict input validation and sanitization on all user-supplied parameters in the OCPP service, utilizing parameterized approaches and input allowlisting to prevent command injection.
Charx Sec 3000/3050/3100/3150 Firmware version 1.5.1 or later
- Identify the specific Charx Sec model (3000, 3050, 3100, or 3150) in use
- Obtain the firmware version 1.5.1 or later from the vendor (Charx)
- Review vendor documentation for firmware upgrade procedures
- Follow the vendor's recommended process to upload and install firmware version 1.5.1 or later
- Verify the firmware upgrade was successful and the device is functioning properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25998 — 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-25998 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