dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2024-39601

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 vulnerability has been identified in CPCI85 Central Processing/Communication (All versions < V5.40), SICORE Base system (All versions < V1.4.0). Affected devices allow a remote authenticated user or an unauthenticated user with physical access to downgrade the firmware of the device. This could allow an attacker to downgrade the device to older versions with known vulnerabilities.

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 · high confidence

This is a firmware downgrade vulnerability in CPCI85 Central Processing/Communication devices (versions < V5.40) and SICORE Base system (versions < V1.4.0). Affected devices allow a remote authenticated attacker or an unauthenticated user with physical access to install older firmware versions that may contain known vulnerabilities, enabling rollback attacks.

MitigationUpgrade CPCI85 firmware to version V5.40 or later and SICORE Base system to version V1.4.0 or later. Implement firmware integrity verification and rollback protection mechanisms to prevent installation of older vulnerable firmware versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checks

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

  1. Identify the device model
    Locate the physical device or its management interface and confirm whether it is a CPCI85 Central Processing/Communication device or a SICORE Base system. Check the device label, web UI header, or CLI banner for the model identifier.
    Affected if The device is a CPCI85 or SICORE Base system
  2. Check the installed firmware version
    Access the device web management interface, CLI, or system information page and locate the firmware version field. Record the exact version string displayed (for example, V5.30 or V1.3.5).
    Affected if The displayed version is below V5.40 for CPCI85 or below V1.4.0 for SICORE
  3. Verify if firmware rollback protection is active
    Navigate to the device security settings, firmware update configuration, or system protection settings. Look for an option labeled rollback protection, anti-rollback, or firmware integrity check. Determine whether it is enabled or disabled.
    Affected if Rollback protection is disabled or unavailable on the device
  4. Confirm firmware upload does not require elevated authentication
    Attempt to access the firmware upload or update function through the web interface or CLI. Observe whether authentication is required, or if a low-privilege or unauthenticated user can initiate a firmware installation.
    Affected if Firmware updates can be performed by a standard user or without authentication

You are affected if your device is a CPCI85 version below V5.40 or a SICORE Base system version below V1.4.0, and firmware rollback protection is disabled or not present.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade CPCI85 firmware to version V5.40 or later and SICORE Base system to version V1.4.0 or later. Implement firmware integrity verification and rollback protection mechanisms to prevent installation of older vulnerable firmware versions.

Recommended fix High confidence

CPCI85: upgrade to V5.40 or later; SICORE Base system: upgrade to V1.4.0 or later

  1. Obtain the firmware update V5.40 for CPCI85 Central Processing/Communication from the official Siemens support portal (cert-portal.siemens.com)
  2. Obtain the firmware update V1.4.0 for SICORE Base system from the official Siemens support portal
  3. Verify the integrity of downloaded firmware files using checksums provided by Siemens
  4. Follow the device-specific firmware upgrade procedure documented in the Siemens user manual for your device model
  5. Apply the firmware update to the affected CPCI85 device, upgrading to version V5.40 or later
  6. Apply the firmware update to the affected SICORE Base system device, upgrading to version V1.4.0 or later
  7. Verify the firmware version has been successfully updated by checking the device firmware version information
  8. Confirm that the device is functioning normally after the upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

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