dbcve.org
Pxc12\/22\/36 E.d FirmwareOperating system · Siemens

CVE-2018-4834

CRITICAL · 9.8 CVSS v3.1 Published 2018-01-24
Fix available
A fix is available. Upgrade to 6.00.204 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Desigo PXC00-E.D V4.10 (All versions < V4.10.111), Desigo PXC00-E.D V5.00 (All versions < V5.0.171), Desigo PXC00-E.D V5.10 (All versions < V5.10.69), Desigo PXC00-E.D V6.00 (All versions < V6.0.204), Desigo PXC00/64/128-U V4.10 (All versions < V4.10.111 only with web module), Desigo PXC00/64/128-U V5.00 (All versions < V5.0.171 only with web module), Desigo PXC00/64/128-U V5.10 (All versions < V5.10.69 only with web module), Desigo PXC00/64/128-U V6.00 (All versions < V6.0.204 only with web module), Desigo PXC001-E.D V4.10 (All versions < V4.10.111), Desigo PXC001-E.D V5.00 (All versions < V5.0.171), Desigo PXC001-E.D V5.10 (All versions < V5.10.69), Desigo PXC001-E.D V6.00 (All versions < V6.0.204), Desigo PXC100-E.D V4.10 (All versions < V4.10.111), Desigo PXC100-E.D V5.00 (All versions < V5.0.171), Desigo PXC100-E.D V5.10 (All versions < V5.10.69), Desigo PXC100-E.D V6.00 (All versions < V6.0.204), Desigo PXC12-E.D V4.10 (All versions < V4.10.111), Desigo PXC12-E.D V5.00 (All versions < V5.0.171), Desigo PXC12-E.D V5.10 (All versions < V5.10.69), Desigo PXC12-E.D V6.00 (All versions < V6.0.204), Desigo PXC200-E.D V4.10 (All versions < V4.10.111), Desigo PXC200-E.D V5.00 (All versions < V5.0.171), Desigo PXC200-E.D V5.10 (All versions < V5.10.69), Desigo PXC200-E.D V6.00 (All versions < V6.0.204), Desigo PXC22-E.D V4.10 (All versions < V4.10.111), Desigo PXC22-E.D V5.00 (All versions < V5.0.171), Desigo PXC22-E.D V5.10 (All versions < V5.10.69), Desigo PXC22-E.D V6.00 (All versions < V6.0.204), Desigo PXC22.1-E.D V4.10 (All versions < V4.10.111), Desigo PXC22.1-E.D V5.00 (All versions < V5.0.171), Desigo PXC22.1-E.D V5.10 (All versions < V5.10.69), Desigo PXC22.1-E.D V6.00 (All versions < V6.0.204), Desigo PXC36.1-E.D V4.10 (All versions < V4.10.111), Desigo PXC36.1-E.D V5.00 (All versions < V5.0.171), Desigo PXC36.1-E.D V5.10 (All versions < V5.10.69), Desigo PXC36.1-E.D V6.00 (All versions < V6.0.204), Desigo PXC50-E.D V4.10 (All versions < V4.10.111), Desigo PXC50-E.D V5.00 (All versions < V5.0.171), Desigo PXC50-E.D V5.10 (All versions < V5.10.69), Desigo PXC50-E.D V6.00 (All versions < V6.0.204), Desigo PXM20-E V4.10 (All versions < V4.10.111), Desigo PXM20-E V5.00 (All versions < V5.0.171), Desigo PXM20-E V5.10 (All versions < V5.10.69), Desigo PXM20-E V6.00 (All versions < V6.0.204). A remote attacker with network access to the device could potentially upload a new firmware image to the devices without prior authentication.

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

This is an unauthenticated remote firmware upload vulnerability in Siemens Desigo PXC building automation controllers. A remote attacker with network access can upload arbitrary firmware images to affected devices without any prior authentication, potentially allowing complete device compromise, code execution, or denial of service.

MitigationUpdate affected devices to the patched versions (V4.10.111, V5.0.171, V5.10.69, V6.0.204 or higher). If immediate patching is not feasible, restrict network access to these devices using network segmentation and firewalls to limit exposure.

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
Pxc12\/22\/36 E.d FirmwareOperating system
Affected:< 6.00.204
Pxc00\/50\/100\/200 E.d FirmwareOperating system
Affected:< 6.00.204
Pxc00\/64\/128 U FirmwareOperating system
Affected:< 6.00.204
Pxc001 E.d FirmwareOperating system
Affected:< 6.00.204
Pxm20 E FirmwareOperating system
Affected:< 6.00.204

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

CVSS:3.1/AV:N/AC:L/PR:N/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 device model
    Locate the Siemens Desigo PXC controller model number on the physical device label or in the device's web interface/system documentation. Confirm it matches one of the affected series: Pxc12/22/36 E.d, Pxc00/50/100/200 E.d, Pxc00/64/128 U, Pxc001 E.d, or Pxm20 E.
    Affected if The device is a Siemens Desigo PXC controller from any of the listed model families.
  2. Determine the installed firmware version
    Access the device's web interface or management console and navigate to the system information or firmware version section. Alternatively, use the device's management software or CLI to query the firmware version.
    Affected if The firmware version is lower than 6.00.204, or is an unpatched version of V4.10.111, V5.0.171, or V5.10.69.
  3. Check if the firmware upload interface is accessible
    From a network perspective, verify if HTTP/HTTPS ports used for firmware updates (typically ports 80/443 or vendor-specific management ports) are reachable on the device. Attempt a controlled request to the firmware upload endpoint if credentials and authorization are available.
    Affected if The firmware upload service is exposed and reachable from the network without authentication.
  4. Assess network exposure of the device
    Review firewall rules, network segmentation, and access control lists to determine if the device management interfaces are accessible from untrusted networks, including the internet or guest network segments.
    Affected if The device has direct network access from external networks or untrusted zones without proper filtering.

The environment is affected if a Siemens Desigo PXC controller runs firmware version lower than 6.00.204 (or an unpatched V4.10.111/V5.0.171/V5.10.69) and has its firmware upload interface exposed to the network.

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 6.00.204 or later
Fixed in 6.00.204
Interim mitigation

Update affected devices to the patched versions (V4.10.111, V5.0.171, V5.10.69, V6.0.204 or higher). If immediate patching is not feasible, restrict network access to these devices using network segmentation and firewalls to limit exposure.

Recommended fix High confidence

Firmware V4.10.111+ / V5.0.171+ / V5.10.69+ / V6.0.204+ (depending on installed branch)

  1. Identify the exact Desigo PXC model and current firmware version installed on the device
  2. Determine which firmware branch is installed (V4.10, V5.00, V5.10, or V6.00)
  3. Download the appropriate firmware update from Siemens official support portal (cert-portal.siemens.com)
  4. For V4.10 branch: upgrade to firmware version V4.10.111 or higher
  5. For V5.00 branch: upgrade to firmware version V5.0.171 or higher
  6. For V5.10 branch: upgrade to firmware version V5.10.69 or higher
  7. For V6.00 branch: upgrade to firmware version V6.0.204 or higher
  8. Backup current device configuration before applying firmware update
Caveat Industrial device firmware upgrades may affect existing configurations or integrations; test in non-production environment first

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

Fix this in Pxc12\/22\/36 E.d Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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