Cyber Resilience

CVE-2024-35425

MediumPublic PoC

Published: 08 November 2024

Published
08 November 2024
Modified
05 June 2025
KEV Added
Patch
CVSS Score v3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS Score 0.0011 28.6th percentile
Risk Priority 11 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2024-35425 is a medium-severity Improper Isolation or Compartmentalization (CWE-653) vulnerability in Lonelycoder Vmir. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked at the 28.6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

EU & UK References

Vulnerability details

vmir e8117 was discovered to contain a segmentation violation via the function_prepare_parse function at /src/vmir_function.c.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Why these techniques?

Segmentation fault and evil memory address write in vmir's WASM parser (function_prepare_parse) via crafted WASM file over HTTP enables remote code execution (T1203: Exploitation for Client Execution) and denial of service (T1499.004: Application or System Exploitation).

Affected Assets

lonelycoder
vmir
2018-08-28

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.

addresses: CWE-653

Defines isolation boundaries by specifying which external systems may access or process organization data.

addresses: CWE-653

Maintains isolation and compartmentalization by restricting flows between security domains or levels.

addresses: CWE-653

Reviewing the continued need for connections supports isolation and compartmentalization.

addresses: CWE-653

Locating systems away from hazards improves isolation and compartmentalization from external physical or environmental threats.

addresses: CWE-653

The CONOPS must articulate isolation and compartmentalization expectations for security and privacy, making architectural failures in separation of duties or domains harder to overlook.

addresses: CWE-653

Security architectures commonly incorporate isolation and compartmentalization strategies to limit the impact of compromises.

addresses: CWE-653

Organization-wide privacy program leadership ensures proper isolation and compartmentalization of personal data.

addresses: CWE-653

Oversight ensures data-matching activities maintain required isolation between distinct data sets and authorized user communities.

References