Security readout for executives and security teams
Plain-English summary
This vulnerability can let an attacker lock KNX building-control devices so legitimate users cannot regain access. Network access to a KNX installation may be enough when devices lack additional security options; physical access can also be sufficient. CISA KEV listing indicates known exploitation, so exposed KNX environments should be treated as urgent.
Executive priority
High priority for facilities, building automation, and ICS teams. The main business risk is loss of control over KNX devices, potentially disrupting building operations and requiring vendor-assisted recovery.
Technical view
CVE-2023-4346 affects KNX devices using KNX Connection Authorization Option 1, depending on implementation. An attacker can purge devices lacking additional security options and set a BCU key, causing denial of access. CVSS 3.1 is 7.5, with network attack vector, low complexity, no privileges, no user interaction, and availability impact.
Likely exposure
Exposure is most likely in KNX building automation installations where devices support Connection Authorization Option 1 and are reachable from a network or physically accessible.
Exploitation context
CISA KEV status supports known exploitation. The provided sources do not include exploit details, affected device models, patch availability, or recovery procedures.
Researcher notes
Evidence is limited to protocol-level behavior and CISA references. Do not generalize to all KNX devices; affected status depends on implementation, Option 1 support, and security configuration.
Mitigation direction
- Inventory KNX devices using Connection Authorization Option 1.
- Check KNX Association and CISA guidance for vendor-specific remediation.
- Restrict network access to KNX installation management interfaces.
- Review physical access controls for KNX devices and cabinets.
- Prioritize devices without additional KNX security options enabled.
Validation and detection
- Confirm whether deployed KNX devices support Connection Authorization Option 1.
- Verify which KNX devices are network-reachable from untrusted segments.
- Check whether additional KNX security options are enabled.
- Review logs or change records for unexpected purges or BCU key changes.
- Document vendor recovery guidance before attempting resets.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-645: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-4346 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6icscertVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- Added to KEVCISA-ADP
CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.
- ADP timelineCISA-ADP
CVE-2023-4346 added to CISA KEV
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-07-15T00:00:00.000Z: CVE-2023-4346 added to CISA KEV
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cisa.gov/news-events/ics-advisories/icsa-23-236-01CVE reference, icscert · government-resource
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-4346CVE reference, CISA-ADP · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Overly Restrictive Account Lockout Mechanism
Overly Restrictive Account Lockout Mechanism represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.