Skip to content
Server Security Center
KEVhigh7.5

CVE-2023-4346: KNX Association KNX Protocol Connection Authorization Option 1 Overly Restrictive Account Lockout Mechanism

KNX Association KNX Protocol Connection Authorization Option 1 · listed in the CISA catalog of actively exploited vulnerabilities since 2026-07-15.

CVSS v3.1 (CVE record)
7.5
high
EPSS (exploit probability, 30 days)
1.4%
higher than 72.4% of all CVEs
Added to CISA KEV
2026-07-15
US federal due date 2026-07-29
Automatable (CISA SSVC)
yes
technical impact: partial

CVE-2023-4346 explained

CVE-2023-4346 is an overly restrictive lockout weakness in KNX devices that use KNX Connection Authorization and support Option 1. Depending on the implementation, an attacker can set a BCU key that locks the device, and owners often cannot reset it without the current password. CISA lists it as known to be exploited, which makes it a priority for building automation operators.

Impact

An attacker with access to a network connected to the KNX installation can purge devices that lack additional security options and set a BCU key, locking the owner out. No privileges or user interaction are needed. The impact is on availability, with no loss of confidentiality or integrity. CISA rates the attack as automatable with partial technical impact. An attacker with physical access to a device that is not networked can cause the same lockout.

Who is affected

The CVE record lists KNX Association KNX Protocol Connection Authorization Option 1 with the version entry 0. Exposure depends on the device implementation. Devices that use KNX Connection Authorization and support Option 1 may be affected. The CVE record names no fixed version. Check the KNX Association guidance and your device manufacturers' instructions for mitigations.

Written with AI from the data on this page and checked against it automatically.

Official description

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.

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • KNX Association KNX Protocol Connection Authorization Option 1
    Affected
    • 0
    Fixed in
    not stated

How to fix it

  • The CVE record names no fixed version – check CISA's required action for updates and mitigations.
  • CISA's deadline for US federal agencies: 2026-07-29 (passed) – a useful benchmark for everyone else, too.

Workaround:

  • The KNX Association recommends users always set the BCU Key in every KNX Project that is already finished and will be commissioned in the future.
  • Handover the BCU Key as part of the Project Documentation to the Building Owner.

What to do

  1. Apply mitigations according to KNX Association and device manufacturer instructions, as CISA's required action states.
  2. Remove KNX installations and their IP interfaces from direct internet exposure and isolate them on restricted network segments.
  3. Enable the additional security options available on your KNX devices so they cannot simply be purged.
  4. Set your own BCU key on devices where supported, store it securely, and limit who can access the KNX network.
  5. Restrict physical access to KNX devices and wiring.
  6. Check for unexpected lockouts or changed device configurations that may indicate compromise.

The CVE record names no fixed version. Follow the KNX Association and device manufacturer guidance and CISA's required action. Apply the vendor's mitigations, keep KNX networks isolated from untrusted and internet-facing networks, enable additional device security options, and restrict physical access. CISA's required action says to discontinue use of the product if mitigations are unavailable.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Partial – limited control or information

Weakness: CWE-645 Overly Restrictive Account Lockout Mechanism

Questions about CVE-2023-4346

Is CVE-2023-4346 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-07-15, with a US federal due date of 2026-07-29. Ransomware use is listed as unknown.
Does the attacker need network access?
Not necessarily. If the device connects to a network, an attacker with access to that network can lock it. A device that is not networked can still be locked by someone with physical access.
What does a successful attack cause?
The device is locked with a BCU key the owner does not know. Users may be unable to reset it to regain access. The impact is on availability only.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.