{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2023-4346 in the wild since at least 15 Jul 2026.","fix":"No fix has been published for CVE-2023-4346 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 29 Jul 2026.","what":"CVE-2023-4346 is a high-severity denial of service vulnerability in KNX Protocol Connection Authorization Option 1, published on 29 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-4346 and fix it if it is affected.\n\nWhat it is: CVE-2023-4346 is a high-severity denial of service vulnerability in KNX Protocol Connection Authorization Option 1, published on 29 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2023-4346 in the wild since at least 15 Jul 2026.\n\nAffected product: KNX Protocol Connection Authorization Option 1. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-4346/ (Markdown: https://insights.sbomify.com/CVE-2023-4346/index.md)","id":"CVE-2023-4346","markdown":"https://insights.sbomify.com/CVE-2023-4346/index.md","name":"CVE-2023-4346","record":{"aliases":["GHSA-qccg-qqvh-pq7q"],"analysis":{"component_type":"ics_ot","fix_type":"configuration_change","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"KNX building automation","requires_auth":"none","summary":"Attackers can lock KNX devices by setting a BCU key, preventing user access and requiring physical intervention to reset.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"connection_authorization","vendor":"knx"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-645","name":"Overly Restrictive Account Lockout Mechanism"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":null,"headline":"KNX Association KNX Protocol Connection Authorization Option 1 Overly Restrictive Account Lockout Mechanism","id":"CVE-2023-4346","indexable":true,"kev":{"dateAdded":"2026-07-15","dueDate":"2026-07-29","knownRansomwareCampaignUse":"Unknown","product":"KNX Protocol Connection Authorization Option 1","requiredAction":"Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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.","vendorProject":"KNX Association","vulnerabilityName":"KNX Association KNX Protocol Connection Authorization Option 1 Overly Restrictive Account Lockout Mechanism Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site Scripting (XSS) - Reflected in librenms/librenms","id":"CVE-2023-4347"},"packages":[],"prev":{"headline":"Broadcom RAID Controller web interface is vulnerable client-side control bypass","id":"CVE-2023-4345"},"products":["KNX Protocol Connection Authorization Option 1"],"published":"2023-08-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"active","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-16","vendors":["KNX Association"]},"summary":"Attackers can lock KNX devices by setting a BCU key, preventing user access and requiring physical intervention to reset.","url":"https://insights.sbomify.com/CVE-2023-4346/"}