dbcve.org
Capital VstarApplication · Siemens

CVE-2019-13939

HIGH · 7.1 CVSS v3.1 Published 2020-01-16
Fix available
A fix is available. Upgrade to 2.8.2 / 2017.02.2 or later.
See remediation →
76/100
Remediation priority · High
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 APOGEE MEC/MBC/PXC (P2) (All versions < V2.8.2), APOGEE PXC Compact (BACnet) (All versions < V3.5.3), APOGEE PXC Compact (P2 Ethernet) (All versions >= V2.8.2 < V2.8.19), APOGEE PXC Modular (BACnet) (All versions < V3.5.3), APOGEE PXC Modular (P2 Ethernet) (All versions >= V2.8.2 < V2.8.19), Capital Embedded AR Classic 431-422 (All versions), Capital Embedded AR Classic R20-11 (All versions < V2303), Desigo PXC00-E.D (All versions >= V2.3 < V6.0.327), Desigo PXC00-U (All versions >= V2.3x and < V6.00.327), Desigo PXC001-E.D (All versions >= V2.3 < V6.0.327), Desigo PXC100-E.D (All versions >= V2.3 < V6.0.327), Desigo PXC12-E.D (All versions >= V2.3 < V6.0.327), Desigo PXC128-U (All versions >= V2.3x and < V6.00.327), Desigo PXC200-E.D (All versions >= V2.3 < V6.0.327), Desigo PXC22-E.D (All versions >= V2.3 < V6.0.327), Desigo PXC22.1-E.D (All versions >= V2.3 < V6.0.327), Desigo PXC36.1-E.D (All versions >= V2.3 < V6.0.327), Desigo PXC50-E.D (All versions >= V2.3 < V6.0.327), Desigo PXC64-U (All versions >= V2.3x and < V6.00.327), Desigo PXM20-E (All versions >= V2.3 < V6.0.327), Nucleus NET (All versions), Nucleus ReadyStart V3 (All versions < V2017.02.3), Nucleus Source Code (All versions), SIMOTICS CONNECT 400 (All versions < V0.3.0.330), TALON TC Compact (BACnet) (All versions < V3.5.3), TALON TC Modular (BACnet) (All versions < V3.5.3). By sending specially crafted DHCP packets to a device where the DHCP client is enabled, an attacker could change the IP address of the device to an invalid value.

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

The DHCP client in the affected devices fails to properly validate DHCP responses, allowing an unauthenticated attacker on the network to send specially crafted DHCP packets that force the device to accept an invalid IP address. This effectively causes a denial of service by making the device unreachable.

MitigationApply vendor-provided firmware updates to reach the patched versions (V2.8.2+, V3.5.3+, V2.8.19+, V6.0.327+, V2303+, V2017.02.3+, V0.3.0.330+). As a compensating control, enable DHCP authentication or use network segmentation to prevent unauthorized DHCP packets.

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
Capital VstarApplication
Affected:all versions
Nucleus NetApplication
Affected:all versions
Nucleus ReadystartApplication
Affected:< 2017.02.2
Nucleus SafetycertApplication
Affected:all versions
Nucleus Source CodeApplication
Affected:all versions
Nucleus RtosOperating system
Affected:all versions
Apogee Modular Equiment Controller FirmwareOperating system
Affected:< 2.8.2
Apogee Modular Building Controller FirmwareOperating system
Affected:< 2.8.2

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 Siemens product in use
    Determine which specific Siemens product from the affected list is deployed: Capital Vstar, Nucleus Net, Nucleus Readystart, Nucleus Safetycert, Nucleus Source Code, Nucleus Rtos, or Apogee Modular Equipment/Building Controller
    Affected if The product is any of the affected Siemens products listed in the CVE (all versions are affected for most products, specific version limits apply for Nucleus Readystart and Apogee controllers)
  2. Check the installed version
    Retrieve the installed firmware or software version of the identified product and compare it against the affected version ranges: Nucleus Readystart versions prior to 2017.02.2, and Apogee Modular Equipment/Building Controller versions prior to 2.8.2
    Affected if The version is below the fixed release or the product has no version limitation (all versions affected)
  3. Confirm DHCP client is enabled
    Verify whether the DHCP client functionality is active on the device, as this vulnerability exists in the DHCP client component
    Affected if DHCP client is enabled and the product/version combination falls within the affected ranges

You are likely affected if you are running any of the affected Siemens products with DHCP client enabled and your version is within the vulnerable range or the product has no version restriction.

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.

From vendor data
Upgrade available Upgrade to 2.8.2 / 2017.02.2 or later
Fixed in 2.8.22017.02.2
Interim mitigation

Apply vendor-provided firmware updates to reach the patched versions (V2.8.2+, V3.5.3+, V2.8.19+, V6.0.327+, V2303+, V2017.02.3+, V0.3.0.330+). As a compensating control, enable DHCP authentication or use network segmentation to prevent unauthorized DHCP packets.

Fix this in Capital Vstar Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
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,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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