PatchTheCVEvmir vulnerabilities and fixes
Recent CVEs affecting vmir, with upgrade or downgrade steps. 7 tracked.
vmir has 7 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2024-11-08. Highest priority: CVE-2024-35426 (score 56/100).
- CVE-2024-35427 MEDIUM 5.5 DOWNGRADE vmir e8117 was discovered to contain a segmentation violation via the export_function function at /src/vmir_wa
- CVE-2024-35426 CRITICAL 9.8 DOWNGRADE vmir e8117 was discovered to contain a stack overflow via the init_local_vars function at /src/vmir_wasm_parse
- CVE-2024-35425 MEDIUM 5.5 DOWNGRADE vmir e8117 was discovered to contain a segmentation violation via the function_prepare_parse function at /src/
- CVE-2024-35424 MEDIUM 5.5 DOWNGRADE vmir e8117 was discovered to contain a segmentation violation via the import_function function at /src/vmir_wa
- CVE-2024-35423 HIGH 7.8 DOWNGRADE vmir e8117 was discovered to contain a heap buffer overflow via the wasm_parse_section_functions function at /
- CVE-2024-35422 HIGH 7.8 DOWNGRADE vmir e8117 was discovered to contain a heap buffer overflow via the wasm_call function at /src/vmir_wasm_parse
- CVE-2024-35421 MEDIUM 5.5 DOWNGRADE vmir e8117 was discovered to contain a segmentation violation via the wasm_parse_block function at /src/vmir_w
FAQ
How do I fix vmir vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is vmir being exploited right now?
None of the tracked vmir CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which vmir CVE should I patch first?
CVE-2024-35426 currently ranks highest (56/100): vmir e8117 was discovered to contain a stack overflow via the init_local_vars function at /src/vmir_wasm_parse.