CVE-2023-41921
Published: 02 July 2024
Summary
CVE-2023-41921 is a critical-severity Download of Code Without Integrity Check (CWE-494) vulnerability in Ncsc (inferred from references). Its CVSS base score is 9.8 (Critical).
Operationally, ranked at the 32.1th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-46398
- 🇳🇱 NCSC-NL: advisories.ncsc.nl
Vulnerability details
A vulnerability allows attackers to download source code or an executable from a remote location and execute the code without sufficiently verifying the origin and integrity of the code. This vulnerability can allow attackers to modify the firmware before uploading…
more
it to the system, thus achieving the modification of the target’s integrity to achieve an insecure state.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
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.