# CASCA evidence receipt — CVE-2023-4346

- Generation: `gen-56ccdaf914f7b4be95b689ccae7dc20d`
- As known: 2026-07-19T05:00:42+00:00
- Comparison: first_public_core_generation
- Score policy: public-priority-v1.0.1
- Conflict: not observed in this generation

## Source assertions

- **CISA-ADP** (independent_enrichment): container — CISA ADP Vulnrichment
  - Observed: 2026-07-19T04:27:06.398189+00:00
  - Citation: https://www.cve.org/CVERecord?id=CVE-2023-4346
- **CVE** (derivative_copy): container — CVE Program Container
  - Observed: 2026-07-19T04:27:06.398189+00:00
  - Citation: https://www.cve.org/CVERecord?id=CVE-2023-4346
- **icscert** (original_assertion): container — 
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. 


  - Observed: 2026-07-19T04:27:06.398189+00:00
  - Citation: https://www.cve.org/CVERecord?id=CVE-2023-4346
- **CISA KEV** (original_assertion): observed_exploitation — KNX Association KNX Protocol Connection Authorization Option 1 Overly Restrictive Account Lockout Mechanism Vulnerability
  - Observed: 2026-07-19T04:54:04.25158+00:00
  - Citation: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- **FIRST EPSS** (original_assertion): model_probability — Probability 0.008550000000; percentile 0.542820000000
  - Observed: 2026-07-19T04:54:35.756809+00:00
  - Citation: https://www.first.org/epss/data_stats.html

## CVSS assessments

- **nvd@nist.gov** (Primary, CVSS 3.1): 7.5 — score eligible
  - Evidence class: nvd_enrichment_exact; source rank: 0
  - Validation: valid_match
  - Vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`
- **ics-cert@hq.dhs.gov** (Secondary, CVSS 3.1): 7.5 — score eligible
  - Evidence class: exact_record_cna; source rank: 1
  - Validation: valid_match
  - Vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`
- **icscert** (unknown, CVSS 3.1): 7.5 — display only
  - Evidence class: direct_cve_record_display_only; source rank: not applicable
  - Validation: display-only direct record assessment
  - Vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`

## Limitations and unknowns

- KEV membership is authoritative for the catalog, not proof of exposure in any environment.
- EPSS is a dated model probability and not an individual-environment prediction.
- Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
- NVD-carried upstream facts remain derivative and are not independent corroboration.
- Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
- NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
- Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
- Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.

Generated from CASCA normalized evidence. This receipt is not proof that an asset is affected, unaffected, safe, or fixed.