dbcve.org
Sinumerik Mc FirmwareOperating system · Siemens

CVE-2022-24408

HIGH · 7.8 CVSS v3.1 Published 2022-03-08
Fix available
A fix is available. Upgrade to 1.15 / 6.15 or later.
See remediation →
80/100
Remediation priority · High
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 SINUMERIK MC (All versions < V1.15 SP1), SINUMERIK ONE (All versions < V6.15 SP1). The sc SUID binary on affected devices provides several commands that are used to execute system commands or modify system files. A specific set of operations using sc could allow local attackers to escalate their 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 · high confidence

A local privilege escalation vulnerability exists in the SUID 'sc' binary on SINUMERIK MC and ONE controllers. The binary provides commands that allow execution of system commands or modification of system files, enabling a local attacker to escalate privileges to root.

MitigationUpgrade SINUMERIK MC to version V1.15 SP1 or later, and SINUMERIK ONE to version V6.15 SP1 or later to remediate this vulnerability.

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
Sinumerik Mc FirmwareOperating system
Affected:< 1.15= 1.15
Sinumerik One FirmwareOperating system
Affected:< 6.15= 6.15

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
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 checks

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

  1. Identify the Sinumerik controller model
    Determine if the system is a Sinumerik MC or Sinumerik ONE controller. Check system documentation, controller nameplate, or use system information commands if available.
    Affected if The system is neither a Sinumerik MC nor One controller, then this specific CVE does not apply.
  2. Locate the 'sc' binary
    Search for the 'sc' binary on the controller system. Common locations for system binaries may include /usr/bin/, /sbin/, or vendor-specific paths. Use 'find' or 'locate' commands to locate the file.
    Affected if The 'sc' binary does not exist on the system, the vulnerability cannot be exploited.
  3. Verify SUID permission on the binary
    Check the file permissions of the 'sc' binary using 'ls -la <path_to_sc>' or 'stat <path_to_sc>'. Look for the 's' flag in the owner execute position (e.g., -rwsr-xr-x).
    Affected if The 'sc' binary is not SUID (does not have the setuid bit set), the privilege escalation path via SUID is not present.
  4. Determine the firmware version
    Check the installed firmware version of the Sinumerik controller. This is typically accessible through the HMI interface under System > System Info, or via vendor-specific diagnostic commands. Compare the displayed version number against the affected ranges.
    Affected if The firmware version is 1.15 or lower on Sinumerik MC, or 6.15 or lower on Sinumerik One. These versions are within the affected range.

A system is affected if it is a Sinumerik MC (firmware version <= 1.15) or Sinumerik One (firmware version <= 6.15) controller that has a SUID 'sc' binary present on the system.

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.15 / 6.15 or later
Fixed in 1.156.15
Interim mitigation

Upgrade SINUMERIK MC to version V1.15 SP1 or later, and SINUMERIK ONE to version V6.15 SP1 or later to remediate this vulnerability.

Recommended fix High confidence

Sinumerik MC: upgrade to V1.15 SP1; Sinumerik One: upgrade to V6.15 SP1

  1. 1. Identify the Sinumerik device model (MC or One) and current firmware version by accessing the device control panel or system information
  2. 2. Obtain the firmware upgrade package from Siemens (V1.15 SP1 for Sinumerik MC or V6.15 SP1 for Sinumerik One)
  3. 3. Create a full backup of the current device configuration and NC data
  4. 4. Upload the firmware upgrade package via the device's firmware update mechanism (typically via SINUMERIK Operate or the service USB interface)
  5. 5. Allow the firmware installation to complete without interrupting power
  6. 6. After reboot, verify the new firmware version is V1.15 SP1 (MC) or V6.15 SP1 (One)
  7. 7. Restore the previously backed-up configuration and NC data
  8. 8. Verify the sc binary permissions or existence have been corrected in the patched version

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

Fix this in Sinumerik Mc 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-2022-24408 — 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-2022-24408 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