CVE-2023-24500
Electra-Air Central Ac Unit Firmware v7 … v8
Raw vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-24500 is a high-severity Download of Code Without Integrity Check (CWE-494) vulnerability in Electra-Air Central Ac Unit Firmware. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique PubPrn (T1216.001); ranked at the 7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-28518
Vulnerability Data
Electra Central AC unit – Adjacent attacker may cause the unit to load unauthorized FW.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 9 hardening rules · 5 OS baselines
—
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Policies can require integrity verification of software prior to installation, reducing risks from unverified downloads.
Blocks installation of components lacking a valid signature, mitigating download or installation of code without integrity checks.
Acquisition and maintenance portions of the strategy drive requirements for integrity verification of downloaded or supplied code.
Mandating integrity control and approved-only changes during development prevents incorporation of code or components lacking integrity validation.
Supply chain protection requires integrity verification of acquired components, directly reducing insertion or tampering of malicious code during delivery.
Reduces exposure to code obtained without integrity verification by requiring assurance processes that confirm authenticity and absence of tampering.
Tamper resistance and detection commonly include integrity verification of code and firmware obtained from external sources.
Component authenticity requires verifying origin/integrity of acquired firmware or software, directly preventing inclusion of code without integrity checks.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Directly requires assessing authenticity/integrity of software before acquisition and use, preventing unverified downloads.
Requires cryptographic integrity protections (signatures/hashes) for data-in-transit, covering downloaded code.
Prevents execution of unauthorized software, blocking the outcome of an unchecked download.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.29's SOURCE reach (code review, static analysis) catches the canonical patterns — curl with -k, URLClassLoader without checksum, firmware update without signature verification — directly in first-party source, and RUNTIME reach (penetration testing) can observe the download behaviour; the remainder is third-party components with this weakness in binary-only form and cases where integrity verification is delegated to external configuration, neither of which the clause's programme sees.
Mandating integrity checks, digital signatures, and origin tracing for ICT components directly reduces the chance that code or firmware lacking an integrity check will be accepted into the organisation’s environment.
A.8.20's network controls (encryption of data in transit per (e), firewalls/filtering per (i), disabling vulnerable protocols per (n)) block some attack vectors for CWE-494 — in-transit modification and unauthorized access to update servers — but the root weakness (the product not verifying integrity of downloaded code) remains, so an attacker who bypasses network controls (e.g., compromises a legitimate server or tricks the client) can still exploit it.
A.8.28 mandates secure coding practices (prohibiting unauthenticated web services, secure design principles, SAST) that would guide developers to verify integrity of downloaded code, but it is a practice-based control whose effect depends on fallible human implementation, consistent with the A.8.28 -> CWE-502 and A.8.28 -> CWE-79 anchors graded at the same rung.
A.8.30 contracts the supplier for secure design, coding and testing practices (8.25-8.29), which carry the preventive effect on this ordinary software weakness; the clause's own mechanism is contractual, so its reach is mediated and fallible in the same way the owner graded A.8.30 -> CWE-134.
A.8.7's malware detection and repair software (guidance f) scans data received over networks and downloads for known malware before use, which blocks some exploitation of CWE-494 by catching malicious payloads in transit. However, the underlying weakness — the product's own lack of integrity verification on downloaded code — remains present and exploitable by zero-day or signature-evading malware, and by adversary-in-the-middle substitution of legitimate-looking updates, which signature-based scanning does not reach.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.
Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.
Oracle Linux 8 (1 rule)
- V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-494
Oracle Linux 9 (1 rule)
- V-271524 OL 9 must check the GPG signature of software packages originating from external software repositories before installation. blocks CWE-494
RHEL 7 (1 rule, 1 more partial)
- V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-494
- V-204448 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-494
RHEL 8 (1 rule)
- V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-494
RHEL 9 (1 rule)
- V-257820 RHEL 9 must check the GPG signature of software packages originating from external software repositories before installation. blocks CWE-494