dbcve.org
Charx Sec 3000 FirmwareOperating system · Phoenixcontact

CVE-2024-25999

HIGH · 7.8 CVSS v3.1 Published 2024-03-12
Fix available
A fix is available. Upgrade to 1.5.1 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
An unauthenticated local attacker can perform a privilege escalation due to improper input validation in the OCPP agent service. 

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 confidence

This vulnerability allows an unauthenticated local attacker to escalate privileges by exploiting improper input validation in the OCPP (Open Charge Point Protocol) agent service. The lack of proper input sanitization enables a local attacker to potentially execute code or commands with elevated privileges.

MitigationImplement strict input validation and sanitization on all user-controlled inputs within the OCPP agent service, along with proper privilege separation to prevent local privilege escalation.

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
Charx Sec 3000 FirmwareOperating system
Affected:< 1.5.1
Charx Sec 3050 FirmwareOperating system
Affected:< 1.5.1
Charx Sec 3100 FirmwareOperating system
Affected:< 1.5.1
Charx Sec 3150 FirmwareOperating system
Affected:< 1.5.1

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and firmware version
    Access the device web interface or use the manufacturer's management tool to view the device information. Look for the model number (Charx Sec 3000, 3050, 3100, or 3150) and the current firmware version installed.
    Affected if The device is a Charx Sec 3000/3050/3100/3150 model AND the firmware version is below 1.5.1 (e.g., 1.4.0, 1.3.2, etc.)
  2. Locate the OCPP agent service
    Check the device configuration or service list to determine if the OCPP (Open Charge Point Protocol) agent service is enabled. This may be visible in the web interface under Services, Network Services, or OCPP settings.
    Affected if The OCPP agent service is enabled and running on the device
  3. Verify OCPP service configuration
    Inspect the OCPP service configuration files or settings. Look for user-controlled inputs such as charge point identifiers, endpoint URLs, or connection parameters that are accepted by the service.
    Affected if The OCPP service accepts external inputs without visible input validation controls or accepts connections from untrusted sources
  4. Check for local user accounts
    Review the device user management or local account settings to see what local user accounts exist and their privilege levels.
    Affected if There are local user accounts with lower privileges that could be escalated through exploitation of the OCPP service

Your environment is affected if you are running a Charx Sec 3000/3050/3100/3150 device with firmware version below 1.5.1 and the OCPP agent service is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.5.1 or later
Fixed in 1.5.1
Interim mitigation

Implement strict input validation and sanitization on all user-controlled inputs within the OCPP agent service, along with proper privilege separation to prevent local privilege escalation.

Recommended fix High confidence

Firmware version 1.5.1 (or later) for Charx Sec 3000/3050/3100/3150

  1. Contact Charx technical support to obtain the official firmware 1.5.1 or later for your specific model (Charx Sec 3000, 3050, 3100, or 3150)
  2. Follow Charx's documented firmware update procedure, typically via the device management interface or USB update mechanism
  3. After upgrading, verify the firmware version displays 1.5.1 or later in the device management interface
  4. Verify the OCPP agent service is functioning normally after the update
Caveat Review Charx release notes for any compatibility considerations with your OCPP backend system before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Charx Sec 3000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25999 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25999 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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