dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2024-41171

HIGH · 8.8 CVSS v3.1 Published 2024-09-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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 828D V4 (All versions), SINUMERIK 828D V5 (All versions < V5.24), SINUMERIK 840D sl V4 (All versions), SINUMERIK ONE (All versions < V6.24). Affected devices do not properly enforce access restrictions to scripts that are regularly executed by the system with elevated privileges. This could allow an authenticated local attacker to escalate their privileges in the underlying system.

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

This is a local privilege escalation vulnerability in Siemens SINUMERIK CNC controllers. Affected devices fail to properly enforce access restrictions on scripts that execute with elevated system privileges. An authenticated local attacker can manipulate these unprotected scripts to gain root/admin-level access to the underlying operating system.

MitigationUpdate SINUMERIK 828D V5 to version V5.24 or later, and SINUMERIK ONE to V6.24 or later. For V4 versions (828D V4, 840D sl V4), contact Siemens for available patches or compensating controls such as restricting local account access and monitoring for unauthorized script modifications.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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 SINUMERIK model and version
    Access the CNC system interface or use system information commands to determine the exact model (828D, 840D sl, or ONE) and installed firmware version
    Affected if Model is 828D V5 with version below V5.24, or ONE with version below V6.24, or any V4 version (828D V4 or 840D sl V4)
  2. Verify local authentication is enabled
    Check system security settings to determine if local user accounts are active on the CNC controller
    Affected if Local authentication is enabled - this is required for the attack vector (authenticated local attacker)
  3. Inspect script directory permissions
    Examine file system permissions on directories containing startup, initialization, or system maintenance scripts that may run with elevated privileges
    Affected if Scripts executable with elevated privileges have weak or missing access controls allowing modification by standard users
  4. Check for unauthorized script modifications
    Compare current scripts in system directories against known-good baselines or verify file integrity of privileged scripts
    Affected if Any scripts that execute with elevated privileges show unexpected modifications or unexpected files present
  5. Review local user account privileges
    Examine which local users have access to modify system scripts or execute commands at elevated privilege levels
    Affected if Standard or unprivileged local users have write access to scripts that run as root or system-level

A system is affected if it is a vulnerable SINUMERIK model/version AND local authenticated access exists AND scripts with elevated privileges lack proper access restrictions.

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

Update SINUMERIK 828D V5 to version V5.24 or later, and SINUMERIK ONE to V6.24 or later. For V4 versions (828D V4, 840D sl V4), contact Siemens for available patches or compensating controls such as restricting local account access and monitoring for unauthorized script modifications.

Recommended fix Moderate confidence

SINUMERIK 828D V5 to V5.24+; SINUMERIK ONE to V6.24+; Contact Siemens for V4 versions

  1. 1. Identify the exact SINUMERIK model and current firmware version installed on the device
  2. 2. For SINUMERIK 828D V5: Upgrade to firmware version V5.24 or later
  3. 3. For SINUMERIK ONE: Upgrade to firmware version V6.24 or later
  4. 4. For SINUMERIK 828D V4 and SINUMERIK 840D sl V4: Contact Siemens for the appropriate fixed firmware version, as all versions are affected
  5. 5. After upgrade, verify that the access controls are properly enforced on privileged scripts
  6. 6. Review user permissions to ensure only authorized personnel have local access
Caveat firmware upgrades on industrial control devices may require revalidation of CNCspecific configurations and compatibility checks with connected systems

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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