CVE-2024-33118
Published: 06 May 2024
Summary
CVE-2024-33118 is a high-severity Download of Code Without Integrity Check (CWE-494) vulnerability in Luckyframe Luckyframeweb. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 38.9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-30863
Vulnerability details
LuckyFrameWeb v3.5.2 was discovered to contain an arbitrary read vulnerability via the fileDownload method in class com.luckyframe.project.common.CommonController.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Arbitrary file read in public-facing web app (T1190) enables data collection from local system (T1005), file discovery via path probing (T1083), and accessing unsecured credentials in files (T1552.001).
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.