CVE-2018-4860
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 SCALANCE M875 (All versions). An authenticated remote attacker with access to the web interface (443/tcp), could execute arbitrary operating system commands. Successful exploitation requires that the attacker has network access to the web interface. The attacker must be authenticated as administrative user to exploit the security vulnerability. The vulnerability could allow an attacker to execute arbitrary code on the device. 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 confidenceCommand injection vulnerability in SCALANCE M875 web interface (443/tcp) allows authenticated administrative users to execute arbitrary operating system commands via the web interface. The attacker needs valid admin credentials to exploit this flaw, which could lead to full device compromise.
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 versionsCVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SCALANCE M875 devices on the networkScan the network for devices responding on port 443/tcp and check the HTTP response header or HTTPS certificate for 'SCALANCE M875' or Siemens branding. Review network topology documentation for presence of this specific model.Affected if A SCALANCE M875 device with web interface enabled is found on the network.
-
Confirm the device model and firmware versionAccess the web interface at https://<device-ip>/ and log in. Navigate to System Information or Device Status page to view the exact firmware version. Compare against the affected product list.Affected if The device is confirmed as a Siemens SCALANCE M875 running any firmware version.
-
Verify web interface accessibilityConfirm port 443/tcp is open and responding on the SCALANCE M875 device using a port scanner (nmap -p 443 <ip>) or by attempting an HTTPS connection.Affected if The web interface on port 443/tcp is accessible from any network segment that contains the device.
-
Check for existing administrative accountsLog into the web interface and navigate to User Management or Administration settings. List all configured administrative users. Default or custom admin accounts both enable exploitation.Affected if One or more administrative user accounts are configured and enabled on the device.
-
Assess network exposure of the web interfaceReview firewall rules, ACLs, or network segmentation to determine if the web interface (443/tcp) is accessible from network segments other than a trusted management network.Affected if The web interface is reachable from network segments beyond a dedicated management VLAN.
If a SCALANCE M875 device with an accessible web interface and at least one administrative account exists in the environment, the device is vulnerable since all firmware versions are affected.
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 dataApply vendor-supplied firmware patches when available; if no patch exists, restrict network access to the web interface using firewall rules or network segmentation, and ensure administrative credentials are strong and changed from defaults. Consider disabling the web interface if not required for operations.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-4860 — 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-4860 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