CVE-2025-24006
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 local attacker can leverage insecure permissions via SSH on the affected devices to escalate privileges to 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 is a local privilege escalation vulnerability where a low-privileged user with SSH access can exploit insecure file or directory permissions to gain root-level access. The vulnerability stems from improper permission settings on system files, configurations, or binaries accessible through the SSH 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.7.3< 1.7.3< 1.7.3< 1.7.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionSSH into the device and run 'cat /etc/version' or 'fw_printenv' or check the web interface for firmware version informationAffected if The device is a Phoenix Contact Charx Sec 3000, 3050, 3100, or 3150 with firmware version below 1.7.3
-
Verify SSH service is accessibleConfirm SSH daemon is running and accepting connections using 'systemctl status sshd' or 'ps aux | grep ssh'Affected if SSH service is enabled and a low-privileged user has access to the device
-
Check for world-writable files in SSH-accessible pathsRun 'find / -perm -002 -type f 2>/dev/null' or specifically check common SSH-accessible paths like /home, /var/www, /opt, /etc, and application directories for world-writable permissionsAffected if World-writable files exist in paths accessible to the low-privileged SSH user
-
Check for group-writable files in SSH-accessible pathsRun 'find / -perm -020 -type f 2>/dev/null' or check paths accessible via SSH for group-writable permissions that grant unnecessary group access
-
Identify SUID/SGID binaries in accessible directoriesRun 'find / -perm -4000 -o -perm -2000 2>/dev/null' to list SUID/SGID binaries, then verify if any are world-readable/writable in SSH-accessible pathsAffected if SUID/SGID binaries exist in directories accessible via SSH and are writable by low-privileged users, allowing privilege escalation
The environment is affected if the device is a Phoenix Contact Charx Sec 3000/3050/3100/3150 running firmware below version 1.7.3, SSH is accessible, and insecure file or directory permissions exist in SSH-accessible paths that could be exploited for privilege escalation.
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.7.3
Review and remediate file/directory permissions on the affected device, ensuring configuration files, scripts, and binaries are not world-writable or group-writable, particularly in paths accessible via SSH. Follow the principle of least privilege and remove unnecessary SUID/SGID binaries.
Firmware version 1.7.3 or later
- Obtain the firmware version 1.7.3 or later from the vendor (Charx) or certified distribution channel
- Review the vendor's official firmware upgrade documentation for Charx Sec 3000/3050/3100/3150 devices
- Upload the firmware to the device management interface or use the vendor-recommended update mechanism
- Apply the firmware update to all affected Charx Sec devices (3000, 3050, 3100, 3150)
- Verify the firmware version after update confirms 1.7.3 or later is installed
- Confirm SSH service is functioning normally post-update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24006 — 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-24006 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