CVE-2024-35427: vmir e8117 was discovered to contain a segmentation violation via the export_function function at /src/vmir_wa

Routine

MEDIUM 5.5DOWNGRADE

CVE-2024-35427 is a medium-severity flaw (CVSS 5.5) affecting vmir. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 95%)
CISA exploited list	No
Weakness	CWE-754
Published	2024-11-08
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: lonelycoder

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-11-08 23:15 UTCPublished CVE record published
2026-06-17 07:34 UTCUpdated Record last modified

lonelycoder vmir DOWNGRADE

Affected: 2018-08-28

Fixed in: no fixed release known

Safe to downgrade to: a release before 2018-08-28

1. Check installed version

apt-cache policy vmir || rpm -q vmir || vmir --version

2. No fixed release: DOWNGRADE to a release before 2018-08-28 (Debian / Ubuntu)

apt-cache madison vmir sudo apt install vmir=<VERSION_BEFORE_2018-08-28> sudo apt-mark hold vmir

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list vmir sudo dnf downgrade vmir-<VERSION_BEFORE_2018-08-28> sudo dnf versionlock add vmir

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-35427?

vmir: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-35427 being exploited?

CVE-2024-35427 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-35427 affect?

CVE-2024-35427 affects vmir. Severity is medium (CVSS 5.5). vmir e8117 was discovered to contain a segmentation violation via the export_function function at /src/vmir_wasm_parser.c.

How urgent is CVE-2024-35427?

Priority 20/100. No elevated risk signals yet.

Related CVEs

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

References

← Back to latest CVEs