CVE-2023-4346
KNX devices that use KNX Connection Authorization and support Option 1 are, depending on the implementation, vulnerable to being locked and users being unable to reset them to gain access to the device. The BCU key feature on the devices can be used to create a password for the device, but this password can often not be reset without entering the current password. If the device is configured to interface with a network, an attacker with access to that network could interface with the KNX installation, purge all devices without additional security options enabled, and set a BCU key, locking the device. Even if a device is not connected to a network, an attacker with physical access to the device could also exploit this vulnerability in the same way.
Scoring
- Severity
- HIGH
- CVSS base score
- 7.5
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS probability
- 0.05%
- CISA KEV
- Known exploited vulnerability
- CWE
- CWE-645
- Published
- 2023-08-29
- Last modified
- 2026-07-16
Affected products
- KNX Association KNX Protocol Connection Authorization Option 1
Weakness type
Related vulnerabilities
- CVE-2026-53982 — Cap-go Console < 12.28.2 Account Deletion DoS via Device Identifier Association
- CVE-2026-25907 — Dell PowerScale OneFS, version 9.13.0.0, contains an overly restrictive account lockout mechanism...
- CVE-2025-5241 — Denial-of-Service Vulnerability in MELSEC iQ-F Series
- CVE-2025-31947 — Repeated LDAP login failures can lock an LDAP account
- CVE-2024-37028 — BIG-IP Next Central Manager vulnerability
- CVE-2024-1722 — Keycloak-core: dos via account lockout