CVE-2018-11460
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 · uneditedA vulnerability has been identified in SINUMERIK 808D V4.7 (All versions), SINUMERIK 808D V4.8 (All versions), SINUMERIK 828D V4.7 (All versions < V4.7 SP6 HF1), SINUMERIK 840D sl V4.7 (All versions < V4.7 SP6 HF5), SINUMERIK 840D sl V4.8 (All versions < V4.8 SP3). A local attacker with elevated user privileges (manufact) could modify a CRAMFS archive so that after reboot the system loads the modified CRAMFS file and attacker-controlled code is executed with root privileges. The security vulnerability could be exploited by an attacker with local access to the affected systems. Successful exploitation requires elevated user privileges (manufact) but no user interaction. The vulnerability could allow an attacker to compromise confidentiality, integrity and availability of the system. At the time of advisory publication no public exploitation of this security vulnerability was known.
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 confidenceA local attacker with manufact-level privileges can modify the CRAMFS (Compressed ROM filesystem) archive on affected Siemens SINUMERIK CNC systems. Upon system reboot, the modified CRAMFS is loaded, executing attacker-controlled code with root privileges.
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 dataall versionsall versions<= 4.7<= 4.7<= 4.8CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the exact Sinumerik model and firmware versionAccess the HMI or use system information commands to retrieve the model number (808d, 828d, or 840d Sl) and firmware version (V4.7 or V4.8 including any SP/HF levels)Affected if The model is Sinumerik 808d V4.7, Sinumerik 808d V4.8, Sinumerik 828d V4.7, Sinumerik 840d Sl V4.7, or Sinumerik 840d Sl V4.8 with version at or below the listed thresholds (4.7, 4.8, or as specified)
-
Check for manufact-level user accountsReview user accounts configured on the system through the HMI user management interface or by examining the user configuration files if accessibleAffected if Manufact-level user accounts exist and are accessible to the attacker, allowing local authentication to the system
-
Verify physical access controls to the CNC deviceInspect the physical location of the CNC machine for proper access controls such as locked cabinets, restricted areas, or tamper-evident sealsAffected if Physical access to the device is not restricted, allowing an attacker to interact with the system directly
-
Assess CRAMFS integrityIf accessible, examine the boot configuration and CRAMFS image files to determine if they can be modified by users with manufact-level privilegesAffected if The CRAMFS filesystem or its configuration files are writable by the manufact-level user or can be modified through physical access
The system is likely affected if it is a Sinumerik 808d, 828d, or 840d Sl running firmware V4.7 or V4.8 at or below the specified version thresholds and the manufact-level user privileges are accessible or physical access to the device is not properly controlled.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataRestrict physical and local access to affected systems, limit manufact-level user privileges, and apply Siemens vendor patches (V4.7 SP6 HF1, V4.7 SP6 HF5, V4.8 SP3 or later) to address this vulnerability.
- Consultation12.0 h
- Implementation20.0 h
- Testing24.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $18,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11460 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-11460 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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