envoyproxy / envoyproxy/envoy

After wasm switched to the wamr engine, the concurrent execution of the wasm plugin reported an error "Exception: out of bounds memory access"

Open
#39,532 13 comments 0 reactions 0 assignees View on GitHub
area/wasm no stalebot question
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 22h
Merged PRs (30d)
430

Description

**If you are reporting *any* crash or *any* potential security issue, *do not*
open an issue in this repo. Please report the issue via emailing
envoy-security@googlegroups.com where the issue will be triaged appropriately.**

*Title*: *One line description*

*Description*:
```
2025-05-19T05:10:06.224165Z error envoy wasm external/envoy/source/extensions/common/wasm/wasm_vm.cc:38 Function: proxy_on_response_headers failed: Exception: out of bounds memory access thread=23
2025-05-19T05:11:27.805264Z error envoy wasm external/envoy/source/extensions/common/wasm/wasm_vm.cc:38 Function: proxy_on_response_headers failed: Exception: out of bounds memory access thread=22
```

envoy build args
```
BAZEL_BUILD_ARGS="--define wasm=wamr"
```

wasm plugin code:https://github.com/proxy-wasm/proxy-wasm-rust-sdk/tree/main/examples/http_headers

[optional *Relevant Links*:]
>Any extra documentation required to understand the issue.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.