CVE-2024-28135
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 · uneditedA low privileged remote attacker can use a command injection vulnerability in the API which performs remote code execution as the user-app user due to improper input validation. The confidentiality is partly affected.
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 is a command injection vulnerability in an API endpoint where improper input validation allows a low-privileged remote attacker to execute arbitrary code on the system. The attacker can achieve remote code execution as the limited 'user-app' user context, resulting in partial confidentiality impact.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
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 modelAccess the device web interface, administrative console, or check the physical device label to confirm the exact model is one of: Charx Sec 3000, Charx Sec 3050, Charx Sec 3100, or Charx Sec 3150Affected if The device model matches one of the four affected product names
-
Check the installed firmware versionLog into the device administrative interface or use the device's firmware version check command (typically via web UI under System > Firmware or via CLI) and note the firmware version numberAffected if The firmware version is 1.5.1 or lower (the vulnerable range is <= 1.5.1)
-
Verify API endpoint exposureDetermine if the device API endpoint is accessible from the network by checking the device network configuration, firewall rules, or attempting a local API request to the vulnerable endpoint path (consult device documentation for the specific API endpoint URL)Affected if The API endpoint is reachable from network locations outside the trusted administrative segment
-
Confirm API authentication settingsCheck the device security configuration to determine if the API endpoint requires authentication and what privilege level is needed to access the vulnerable endpointAffected if The API endpoint allows access from low-privileged or unauthenticated remote attackers
-
Check for signs of compromiseReview device logs, process lists, or network traffic logs for unexpected commands, unusual API calls, or evidence of shell command execution originating from the API interfaceAffected if Logs show unauthorized command execution or unexpected shell invocations
You are affected if your device is a Phoenixcontact Charx Sec 3000/3050/3100/3150 with firmware version 1.5.1 or lower AND the API endpoint is network-accessible to untrusted users.
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 strict input validation and sanitization for all API parameters, preferably using allowlist validation or safe API methods that avoid shell command execution. Consider implementing API request validation frameworks and least-privilege execution contexts.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28135 — 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-28135 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