KNX Connection Authorization Option 1 Device Lockout
CVE-2023-4346 is an overly restrictive account lockout mechanism vulnerability in implementations of KNX Connection Authorization that support Option 1. Affected devices use a BCU key to establish a device password, but the key often cannot be reset without knowledge of the current password. An attacker able to access the KNX installation over its connected network, or able to physically access a device, can purge devices that lack additional security options and set a BCU key. This can permanently lock legitimate owners out of affected devices.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation causes a high-impact availability failure: legitimate operators can lose the ability to access or reset affected KNX devices. This can disrupt KNX building-automation installations and their dependent functions. In many implementations, recovery may not be possible through normal reset procedures and may require hardware replacement.
If you can’t patch tonight, do this now.
Isolate KNX installations from untrusted networks, strictly limit access to networks capable of communicating with KNX devices, and enforce physical security for devices and installation interfaces. Enable additional KNX security options where available, inventory devices using Connection Authorization Option 1, and restrict administrative or commissioning access to authorized personnel.
Patch, then assume compromise.
Apply vendor-specific updates, configuration changes, or guidance for affected KNX devices. Where supported, migrate away from Connection Authorization Option 1 and enable stronger or additional security options. Replace devices that cannot be recovered or remediated through supported vendor procedures.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
29 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.