dbcve.org
Charx Sec 3150 FirmwareOperating system · Phoenixcontact

CVE-2024-3913

MEDIUM · 5.9 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 1.6.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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 remote attacker can use this vulnerability to change the device configuration due to a file writeable for short time after system startup.

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

An unauthenticated remote attacker can modify device configuration due to a race condition where a configuration file remains writeable for a brief window immediately after system startup. This time-of-check to time-of-use (TOCTOU) issue allows configuration changes without authentication during the vulnerable startup period.

MitigationRestrict file permissions immediately upon system startup before network services become available, or implement authentication checks even during the initialization phase to prevent unauthenticated configuration modifications.

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

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/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 the Charx Sec model number
    Locate the device label or check the device web interface/system information to confirm whether the unit is a Sec 3000, 3050, 3100, or 3150 model.
    Affected if The device is any of these four models.
  2. Check the installed firmware version
    Access the device web interface or use the manufacturer's management tool to view the firmware version. Compare it against the affected versions: any build prior to 1.6.3.
    Affected if The firmware version is below 1.6.3.
  3. Verify configuration file permissions during operation
    If you have shell or diagnostic access, examine the configuration file permissions using 'ls -la' or equivalent. Check whether the config file is world-writable or group-writable when the system is in a normal running state.
    Affected if The configuration file remains writable by unauthorized users after startup completes.
  4. Determine network service startup timing
    Review the device boot sequence logs or documentation to confirm whether network services become available before file permissions are restricted. Look for the window between network interface activation and permission lock-down.
    Affected if Network services start before configuration file permissions are locked, creating the TOCTOU window.
  5. Confirm authentication enforcement during boot
    Test or review whether the device requires authentication for configuration changes during the startup phase. Attempt a configuration change request immediately after reboot, before the system is fully initialized.
    Affected if Configuration modifications can be performed without authentication during the startup window.

You are affected if you have a Charx Sec 3000/3050/3100/3150 device running firmware version 1.6.3 or lower, and the device allows unauthenticated configuration changes during its startup phase.

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.6.3 or later
Fixed in 1.6.3
Interim mitigation

Restrict file permissions immediately upon system startup before network services become available, or implement authentication checks even during the initialization phase to prevent unauthenticated configuration modifications.

Recommended fix Moderate confidence

Firmware version 1.6.3 for Charx Sec 3000/3050/3100/3150

  1. Identify the exact model of Charx Sec device (3000, 3050, 3100, or 3150) from the hardware label
  2. Navigate to the vendor's support or download page at cert.vde.com
  3. Download firmware version 1.6.3 or later for your specific model
  4. Review the firmware upgrade instructions provided by the vendor
  5. Connect to the device management interface (web UI or management console)
  6. Backup the current device configuration before proceeding
  7. Upload and apply firmware version 1.6.3 or later
  8. Verify the firmware upgrade was successful

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

Fix this in Charx Sec 3150 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3913 — 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-3913 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