Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2023-26489

9.9 · CRITICAL

wasmtime is a fast and secure runtime for WebAssembly.

Published Mar 8, 2023CWE-125EPSS 1.25%

Overview

CVE-2023-26489 is a critical-severity vulnerability. It was published on March 8, 2023 and has a CVSS 3.1 base score of 9.9 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.9, rated CRITICAL. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

wasmtime is a fast and secure runtime for WebAssembly. In affected versions wasmtime's code generator, Cranelift, has a bug on x86_64 targets where address-mode computation mistakenly would calculate a 35-bit effective address instead of WebAssembly's defined 33-bit effective address. This bug means that, with default codegen settings, a wasm-controlled load/store operation could read/write addresses up to 35 bits away from the base of linear memory. Due to this bug, however, addresses up to `0xffffffff * 8 + 0x7ffffffc = 36507222004 = ~34G` bytes away from the base of linear memory are possible from guest code. This means that the virtual memory 6G away from the base of linear memory up to ~34G away can be read/written by a malicious module. A guest module can, without the knowledge of the embedder, read/write memory in this region. The memory may belong to other WebAssembly instances when using the pooling allocator, for example. Affected embedders are recommended to analyze preexist

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refdocs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.static_memory_guard_sizeRefdocs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.static_memory_maximum_sizeGitHubgithub.com/bytecodealliance/wasmtime/commit/63fb30e4b4415455d47b3da5a19d79c12f4f2d1fGitHubgithub.com/bytecodealliance/wasmtime/security/advisories/GHSA-ff4p-7xrq-q5r8Refgroups.google.com/a/bytecodealliance.org/g/sec-announce/c/Mov-ItrNJsQRefdocs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.static_memory_guard_sizeRefdocs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.static_memory_maximum_sizeGitHubgithub.com/bytecodealliance/wasmtime/commit/63fb30e4b4415455d47b3da5a19d79c12f4f2d1fGitHubgithub.com/bytecodealliance/wasmtime/security/advisories/GHSA-ff4p-7xrq-q5r8Refgroups.google.com/a/bytecodealliance.org/g/sec-announce/c/Mov-ItrNJsQ

How CyberStrike helps

Frequently asked questions

What is CVE-2023-26489?

CVE-2023-26489 is a critical-severity vulnerability. It was published on March 8, 2023 and has a CVSS 3.1 base score of 9.9 (CRITICAL).

How severe is CVE-2023-26489?

This vulnerability has a CVSS 3.1 base score of 9.9, rated CRITICAL. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2023-26489?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2023-26489?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2023-26489 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related CRITICAL CVEs from 2023

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999