How severe is CVE-2017-18868?

CVE-2017-18868 has a CVSS 3.x base score of 7.7, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2017-18868 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (52nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-18868?

CVE-2017-18868 affects Digi Xbee 2 Firmware. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2017-18868?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2017-18868 published?

CVE-2017-18868 was published on 2020-05-21 and last updated on 2026-06-17.

CVE-2017-18868

CVE-2017-18868 is a high-severity vulnerability in Digi Xbee 2 Firmware with a CVSS 3.x base score of 7.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-276.

Key facts

Severity: High (CVSS 3.x base score 7.7)
CVSS v2: 5.5
EPSS exploit prediction: 1% (52nd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-276
Affected product: Digi Xbee 2 Firmware
Published: 2020-05-21
Last modified: 2026-06-17

Description

Digi 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.

Frequently asked questions

What is CVE-2017-18868?: Digi 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.
How severe is CVE-2017-18868?: CVE-2017-18868 has a CVSS 3.x base score of 7.7, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2017-18868 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (52nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-18868?: CVE-2017-18868 affects Digi Xbee 2 Firmware. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-18868?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-18868 published?: CVE-2017-18868 was published on 2020-05-21 and last updated on 2026-06-17.

References

https://www.hindawi.com/journals/scn/2017/1723658/

Affected products (1)

cpe:2.3:o:digi:xbee_2_firmware:-:*:*:*:*:*:*:*

Other CWE-276 (Incorrect Default Permissions) vulnerabilities

CVE-2022-42150 — Critical (CVSS 10.0): TinyLab linux-lab v1.1-rc1 and cloud-labv0.8-rc2, v1.1-rc1 are vulnerable to insecure permissions. The default…
CVE-2020-29492 — Critical (CVSS 10.0): Dell Wyse ThinOS 8.6 and prior versions contain an insecure default configuration vulnerability. A remote…
CVE-2020-29491 — Critical (CVSS 10.0): Dell Wyse ThinOS 8.6 and prior versions contain an insecure default configuration vulnerability. A remote…
CVE-2025-40585 — Critical (CVSS 9.9): A vulnerability has been identified in Energy Services (All versions with G5DFR). Affected solutions using G5DFR…
CVE-2019-19896 — Critical (CVSS 9.9): In IXP EasyInstall 6.2.13723, there is Remote Code Execution via weak permissions on the Engine Service share. The…
CVE-2020-37129 — Critical (CVSS 9.8): Memu Play 7.1.3 contains an insecure folder permissions vulnerability that allows low-privileged users to modify the…

Browse all CWE-276 (Incorrect Default Permissions) vulnerabilities →