bytecodealliance wasm-micro-runtime up to 2.4.0 IPv4 Address exposure of resource

Summaryinfo

A vulnerability marked as problematic has been reported in bytecodealliance wasm-micro-runtime up to 2.4.0. The impacted element is an unknown function of the component IPv4 Address Handler. This manipulation causes exposure of resource. The identification of this vulnerability is CVE-2025-54126. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in bytecodealliance wasm-micro-runtime up to 2.4.0. Affected by this vulnerability is an unknown code of the component IPv4 Address Handler. The manipulation with an unknown input leads to a exposure of resource vulnerability. The CWE definition for the vulnerability is CWE-668. The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource. As an impact it is known to affect confidentiality. The summary by CVE is:

The WebAssembly Micro Runtime's (WAMR) iwasm package is the executable binary built with WAMR VMcore which supports WebAssembly System Interface (WASI) and command line interface. In versions 2.4.0 and below, iwasm uses --addr-pool with an IPv4 address that lacks a subnet mask, allowing the system to accept all IP addresses. This can unintentionally expose the service to all incoming connections and bypass intended access restrictions. Services relying on --addr-pool for restricting access by IP may unintentionally become open to all external connections. This may lead to unauthorized access in production deployments, especially when users assume that specifying an IP without a subnet mask implies a default secure configuration. This is fixed in version 2.4.1.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2025-54126 since 07/17/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 2.4.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 121232a9957a069bbb04ebda053bdc72ab409e7a is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• bytecodealliance

Name

• wasm-micro-runtime

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4.0

License

• open-source

Website

• Product: https://github.com/bytecodealliance/wasm-micro-runtime/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion