CVE-2021-31885
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 APOGEE MBC (PPC) (BACnet) (All versions), APOGEE MBC (PPC) (P2 Ethernet) (All versions), APOGEE MEC (PPC) (BACnet) (All versions), APOGEE MEC (PPC) (P2 Ethernet) (All versions), APOGEE PXC Compact (BACnet) (All versions < V3.5.4), APOGEE PXC Compact (P2 Ethernet) (All versions < V2.8.19), APOGEE PXC Modular (BACnet) (All versions < V3.5.4), APOGEE PXC Modular (P2 Ethernet) (All versions < V2.8.19), Desigo PXC00-E.D (All versions >= V2.3 and < V6.30.016), Desigo PXC00-U (All versions >= V2.3 and < V6.30.016), Desigo PXC001-E.D (All versions >= V2.3 and < V6.30.016), Desigo PXC100-E.D (All versions >= V2.3 and < V6.30.016), Desigo PXC12-E.D (All versions >= V2.3 and < V6.30.016), Desigo PXC128-U (All versions >= V2.3 and < V6.30.016), Desigo PXC200-E.D (All versions >= V2.3 and < V6.30.016), Desigo PXC22-E.D (All versions >= V2.3 and < V6.30.016), Desigo PXC22.1-E.D (All versions >= V2.3 and < V6.30.016), Desigo PXC36.1-E.D (All versions >= V2.3 and < V6.30.016), Desigo PXC50-E.D (All versions >= V2.3 and < V6.30.016), Desigo PXC64-U (All versions >= V2.3 and < V6.30.016), Desigo PXM20-E (All versions >= V2.3 and < V6.30.016), Nucleus NET (All versions), Nucleus ReadyStart V3 (All versions < V2017.02.4), Nucleus ReadyStart V4 (All versions < V4.1.1), Nucleus Source Code (All versions), PLUSCONTROL 1st Gen (All versions), TALON TC Compact (BACnet) (All versions < V3.5.4), TALON TC Modular (BACnet) (All versions < V3.5.4). TFTP server application allows for reading the contents of the TFTP memory buffer via sending malformed TFTP commands. (FSMD-2021-0009)
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 confidenceA vulnerability in the TFTP server component allows remote attackers to read the contents of the TFTP memory buffer by sending malformed TFTP commands, leading to information disclosure. This affects multiple Siemens building automation controllers including APOGEE MBC/MEC, PXC Compact/Modular, Desigo PXC series, and Nucleus-based products.
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< 2017.02.4< 4.1.1all versionsall versionsall versionsall 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify TFTP server is runningCheck if the TFTP service is enabled or listening on UDP port 69. On Linux: 'netstat -uan | grep 69' or 'ss -uan | grep 69'. On embedded devices, check the service status via the admin interface or 'ps' command if SSH is available.Affected if TFTP server is active and exposed on the network
-
Identify the product nameDetermine if the device is one of the affected Siemens building automation controllers: APOGEE MBC, APOGEE MEC, PXC Compact, PXC Modular, Desigo PXC series, or a Nucleus-based product. Check the device label, admin UI, or system information page.Affected if Device is any of the listed Siemens building automation controllers or Nucleus-based products
-
Determine the firmware or software versionAccess the device admin interface, check system information page, or use commands like 'show version', 'ver', or read the firmware file name. For Nucleus products, check the version reported by the software or boot messages.Affected if Version cannot be determined or is unknown
-
Compare against affected version rangesFor Nucleus Readystart V3: version must be >= 2017.02.4 to be patched. For Nucleus Readystart V4: version must be >= 4.1.1 to be patched. For all other listed products (Capital Vstar, Nucleus Net, Apogee Firmware variants): ALL versions are affected since no safe version range is specified.Affected if Nucleus Readystart V3 < 2017.02.4, Nucleus Readystart V4 < 4.1.1, or any version of Capital Vstar, Nucleus Net, Apogee MBC/MEC Firmware, or Apogee Pxc Compact Firmware
The environment is affected if TFTP server is enabled and the device is any Siemens building automation controller or Nucleus-based product with a version that falls within or below the unpatched ranges listed.
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.
dbcve · scoped4.1.12017.02.4
Upgrade affected devices to the patched version (APOGEE/TALON: V3.5.4+ for BACnet, V2.8.19+ for P2 Ethernet; Desigo: V6.30.016+). For products with no patch available, disable TFTP services or isolate devices on a restricted network segment.
V3.5.4 for BACnet variants; V2.8.19 for P2 Ethernet variants; V6.30.016 for Desigo PXC devices; V2017.02.4 for Nucleus ReadyStart V3; V4.1.1 for Nucleus ReadyStart V4
- For APOGEE PXC Compact (BACnet): Upgrade to firmware version V3.5.4 or later
- For APOGEE PXC Compact (P2 Ethernet): Upgrade to firmware version V2.8.19 or later
- For APOGEE PXC Modular (BACnet): Upgrade to firmware version V3.5.4 or later
- For APOGEE PXC Modular (P2 Ethernet): Upgrade to firmware version V2.8.19 or later
- For Desigo PXC00-E.D, PXC00-U, PXC001-E.D, PXC100-E.D, PXC12-E.D, PXC128-U, PXC200-E.D, PXC22-E.D, PXC22.1-E.D, PXC36.1-E.D, PXC50-E.D, PXC64-U, PXM20-E: Upgrade to firmware version V6.30.016 or later
- For Nucleus ReadyStart V3: Upgrade to version V2017.02.4 or later
- For Nucleus ReadyStart V4: Upgrade to version V4.1.1 or later
- For APOGEE MBC/MEC (all variants), Nucleus NET, Nucleus Source Code, PLUSCONTROL 1st Gen, and TALON TC Compact/Modular: Contact Siemens for patched firmware; no specific fixed version listed in available documentation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-31885 — 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-2021-31885 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