CVE-2023-20100
Cisco Ios Xe 17.10.1
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-20100 is a medium-severity Use of Multiple Resources with Duplicate Identifier (CWE-694) vulnerability in Cisco Ios Xe. Its CVSS base score is 6.8 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked in the top 45% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-24279
Vulnerability Data
A vulnerability in the access point (AP) joining process of the Control and Provisioning of Wireless Access Points (CAPWAP) protocol of Cisco IOS XE Software for Wireless LAN Controllers (WLCs) could allow an unauthenticated, remote attacker to cause a denial…
more
of service (DoS) condition on an affected device. This vulnerability is due to a logic error that occurs when certain conditions are met during the AP joining process. An attacker could exploit this vulnerability by adding an AP that is under their control to the network. The attacker then must ensure that the AP successfully joins an affected wireless controller under certain conditions. Additionally, the attacker would need the ability to restart a valid AP that was previously connected to the controller. A successful exploit could allow the attacker to cause the affected device to restart unexpectedly, resulting in a DoS condition.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V8.4.1V3.5.4V6.8.1V9.2.4
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Maintaining software/service inventories requires and enforces unique identifiers to avoid collisions.
Lifecycle management of assets includes identifier uniqueness as a supporting practice.
Managing identities and credentials for users/services/hardware directly requires unique identifiers.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.5.16(e) directly requires avoiding duplicate identities in one domain (the exact condition CWE-694 names), and (a)-(c) further constrain identity issuance to prevent the duplicate-identifier situation from arising; this stops exploitation in the identity-management slice of the weakness but leaves other resource types (non-identity) and cross-domain cases untouched.
Secure development lifecycle practices can catch duplicate-ID issues during design and code review.