dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-31485

HIGH · 7.2 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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.30), SICORE Base system (All versions < V1.3.0). The web interface of affected devices is vulnerable to command injection due to missing server side input sanitation. This could allow an authenticated privileged remote attacker to execute arbitrary code with root privileges.

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

The CPCI85 and SICORE Base system web interfaces suffer from a command injection vulnerability due to missing server-side input sanitation. An authenticated privileged attacker can inject arbitrary OS commands through unsanitized input fields, which are then executed with root privileges on the underlying system.

MitigationUpgrade to CPCI85 version V5.30 or later, or SICORE Base system V1.3.0 or later, which contain the vendor patch for proper server-side input validation. If upgrading is not immediately possible, restrict access to the web interface to trusted users only.

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

CVSS:3.1/AV:N/AC:L/PR:H/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 if CPCI85 or SICORE Base web interface is exposed
    Check network listening services on the target system using 'netstat -tuln | grep -E "(80|443|8080|8443)"' or review firewall rules to see if web interface ports are accessible from untrusted networks
    Affected if The web interface HTTP/HTTPS ports are open and accessible from untrusted networks
  2. Determine installed version of CPCI85
    Check the application version file or binary. Common paths include checking the firmware version via 'cat /proc/version' or looking for version files in '/opt/cpci85/' or similar installation directories. If web interface is accessible, log in and check the 'About' or 'System Information' page for the version number
    Affected if The installed version is lower than V5.30 (e.g., V5.20, V5.10, etc.) or the version cannot be determined but the product is CPCI85
  3. Determine installed version of SICORE Base system
    Check the application version via system files or the web interface. Look for version information in '/opt/sicore/' or similar installation directories, or log into the web interface and navigate to System Settings or About section to identify the build version
    Affected if The installed version is lower than V1.3.0 (e.g., V1.2.x, V1.1.x, V1.0.x) or version cannot be determined but the product is SICORE Base
  4. Verify if authentication is enabled on the web interface
    Attempt to access the web interface without credentials. Check if login page requires username/password, and verify that default credentials have been changed. Review authentication configuration files in the application directory
    Affected if The web interface allows unauthenticated access or uses default/weak credentials, combined with a version prior to the fixed releases

The system is affected if it runs CPCI85 versions before V5.30 or SICORE Base versions before V1.3.0, has the web interface exposed, and an attacker can authenticate to the web interface to inject commands through unsanitized input fields.

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 to CPCI85 version V5.30 or later, or SICORE Base system V1.3.0 or later, which contain the vendor patch for proper server-side input validation. If upgrading is not immediately possible, restrict access to the web interface to trusted users only.

Recommended fix High confidence

CPCI85: upgrade to V5.30 or later; SICORE Base system: upgrade to V1.3.0 or later

  1. Identify which affected product is in use: CPCI85 Central Processing/Communication or SICORE Base system
  2. Contact Siemens or SICORE vendor to obtain the patched version (V5.30 for CPCI85, V1.3.0 for SICORE Base system)
  3. Review vendor release notes and upgrade documentation before proceeding
  4. Schedule a maintenance window for the upgrade
  5. Upgrade the device to the fixed version (V5.30 or higher for CPCI85, V1.3.0 or higher for SICORE Base system)
  6. Verify the web interface is accessible after upgrade
  7. Confirm the command injection vulnerability is remediated
Caveat Review vendor documentation for any configuration or compatibility changes in the new version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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