dbcve.org
Charx Sec 3000 FirmwareOperating system · Phoenixcontact

CVE-2024-6788

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 1.6.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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
A remote unauthenticated attacker can use the firmware update feature on the LAN interface of the device to reset the password for the predefined, low-privileged user “user-app” to the default password.

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

A critical authentication bypass vulnerability allows unauthenticated attackers on the LAN to exploit the firmware update mechanism and reset the password of the predefined 'user-app' account to its default value, enabling unauthorized device access.

MitigationRestrict LAN access to trusted networks, implement authentication requirements for firmware update functions, and apply vendor firmware patches when available. Immediately change the default password for the user-app account if still at default.

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.6.3
Charx Sec 3050 FirmwareOperating system
Affected:< 1.6.3
Charx Sec 3100 FirmwareOperating system
Affected:< 1.6.3
Charx Sec 3150 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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
    Locate the Phoenixcontact Charx Sec device on the network or physically inspect the hardware label. Confirm it is one of: Sec 3000, Sec 3050, Sec 3100, or Sec 3150.
    Affected if Device model is Charx Sec 3000, 3050, 3100, or 3150.
  2. Check firmware version
    Access the device web interface or use SNMP/CLI to retrieve the firmware version. Compare the installed version against the affected range of < 1.6.3.
    Affected if Firmware version is below 1.6.3.
  3. Verify firmware update accessibility
    From a host on the LAN, attempt to reach the firmware update endpoint (typically /fwupdate or /update) without providing any authentication credentials. Check if the HTTP request returns a success response rather than an authentication error.
    Affected if Firmware update interface is accessible without authentication.
  4. Inspect user-app account status
    Log into the device admin interface and examine the 'user-app' account. Verify whether the password has been changed from the factory default or still uses the default credential.
    Affected if The 'user-app' account password remains at factory default setting.

The environment is affected if the device is a Charx Sec 3000/3050/3100/3150 running firmware below version 1.6.3, with the firmware update mechanism exposed to unauthenticated LAN access and the 'user-app' account using its default password.

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 LAN access to trusted networks, implement authentication requirements for firmware update functions, and apply vendor firmware patches when available. Immediately change the default password for the user-app account if still at default.

Recommended fix High confidence

Charx Sec 3000/3050/3100/3150 Firmware 1.6.3

  1. Obtain Charx Sec 3000/3050/3100/3150 firmware version 1.6.3 or later from the vendor (Charx)
  2. Access the device web interface or use the vendor-provided firmware update mechanism
  3. Upload and apply firmware version 1.6.3 or later following the vendor's documented firmware update procedure
  4. After the firmware update completes successfully, change the default password for the 'user-app' account to a strong, unique password

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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