CVE-2017-18868
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 · uneditedDigi XBee 2 devices do not have an effective protection mechanism against remote AT commands, because of issues related to the network stack upon which the ZigBee protocol is built.
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 confidenceDigi XBee 2 devices have a vulnerability where remote AT commands can be executed without effective protection, allowing attackers to potentially reconfigure device settings remotely. This stems from weaknesses in the network stack underlying the ZigBee protocol implementation.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/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.
-
Confirm device model is Digi XBee 2Query the device for its model identifier using the AT command 'ATND' (Node Discover) or by reading the device's IEEE address and checking the manufacturer/OEM documentation to verify it is a Digi XBee 2 ZigBee moduleAffected if The device is confirmed to be a Digi XBee 2 ZigBee module
-
Check firmware versionEnter command mode on the XBee device (typically by sending '+++' within the guard time) and issue the 'ATVR' command to read the firmware version, or use ATFR to read firmware revisionAffected if Any firmware version is installed on a Digi XBee 2 device since all versions are affected
-
Verify remote AT command functionality is enabledEnter command mode and issue 'ATAP' to check the API mode setting, then check if the device accepts remote AT command API frames (0x17 Remote AT Command Request). Also verify if AT command pass-through is enabled via 'ATCP' if supported by the firmwareAffected if Remote AT command functionality (API mode accepting 0x17 frames) is enabled and accessible over the network
-
Assess network exposure of the XBee deviceReview network segmentation and firewall rules to determine if the XBee mesh network or serial interface is exposed to untrusted networks. Check if the device is directly reachable from network segments outside the trusted operational technology networkAffected if The XBee device or its coordinator is reachable from untrusted network segments
-
Check for command mode securityEnter command mode and issue 'ATCM' to check Command Mode Timeout settings, and verify if any command guard parameters are configured. Check if encryption keys are properly set via 'ATKY'Affected if Command mode timeout is disabled or set too high, or if no encryption is configured, allowing easier remote command injection
A user is affected if they have a Digi XBee 2 device on their network with remote AT command functionality enabled and the device is accessible from an untrusted network segment, regardless of firmware version.
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 dataImplement network segmentation to isolate XBee devices from untrusted networks, apply vendor firmware updates when available, and disable remote AT command functionality if not required for operation.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18868 — 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-2017-18868 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