Connection Authorization
Approved changes feed: RSS · Atom
cpe:2.3:a:knx:connection_authorization:-:*:*:*:*:*:*:*
part: a version: - update: *
| Vendor | Knx (f4bafbd8-487f-5d59-9f87-9368b4597fc5) |
|---|---|
| Product | Connection Authorization (02e53ddc-e873-5530-a2c2-48d6b1b61e93) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-4346 |
vulnerable | 2026-06-08 06:16:12.163724 |
Details available
HIGH (7.5)
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.
Published: 2023-08-29T19:38:55.399Z
Updated: 2026-07-16T03:55:23.364Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.