Open nickamorim opened 1 year ago
Adding @weisisea @mattklein123 as extension owners.
i'm fixing this bug @nickamorim and adding a test for this. You can assign this to me @yanavlasov
apologies for causing this crash, I've fixed this issue and re-introduced the test that exercises this. Apologies for not thinking through when I removed the unit test ( it was clearly there for a reason - lesson learnt :) ).
Definitely no need to apologize @deveshkandpal1224 - thank you for such a quick turnaround time!
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: redis: Envoy segfaults when no catch-all-route specified in v1.27
Description:
When there is no catch-all route specified and a request is made to a route that does not have a corresponding prefix_route, Envoy segfaults.
This is likely due to https://github.com/envoyproxy/envoy/pull/27902 since
value
is being set tocatch_all_route
by default if a key doesn't match a prefix route. Ifcatch_all_route
is null (which is the case if no catch_all_route is specified), this will raise a NullPointerException. The test to check if for a missing catch all route was removed as part of that same PR -- https://github.com/envoyproxy/envoy/pull/27902/files#diff-a340d81bca2cdf585a8843b8de21af05aa68578de7e547b8393b487675449ef9L52-L64.Repro steps:
I simply ran
envoy -c config.yaml
with the config pasted below locally and in another terminalredis-cli -p 6380 get key
.Config:
Logs:
Call Stack: