You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 [email protected] where the issue will be triaged appropriately.
Title: Memory overwrite occurring during debug build/testing triggered by protobuf PackFrom
raw_metadata_fetcher_ will be overwritten and cause a test crash.
I'm not familiar enough with the internals of protobuf to know whether the protobuf setup in utility.cc is correct, however it appears to be common from a quick scan through other code.
I'm also not sure if this line is specifically the issue, or its prior to this line in the cluster setup that is the problem.
Would really appreciate some guidance on how to troubleshoot this any further. Unfortunately this crash is highly memory dependent and doesn't occur from a main build, so this is reproducible only in my fork.
Call Stack:
This call stack is generated by watchpoint on raw_metadata_fetcher_
nbaws
changed the title
aws: Memory overwirte protobuf issue triggered by PackFrom
aws: Memory overwrite protobuf issue triggered by PackFrom
May 14, 2024
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
[email protected] where the issue will be triaged appropriately.
Title: Memory overwrite occurring during debug build/testing triggered by protobuf PackFrom
Description:
This line
envoy/source/extensions/common/aws/utility.cc
Line 367 in f0c2329
Causes a memory overwrite corrupting test cases from here:
envoy/test/extensions/common/aws/credentials_provider_impl_test.cc
Line 2325 in f0c2329
Repro steps:
Needs lldb to repro.
In most cases
envoy/test/extensions/common/aws/credentials_provider_impl_test.cc
Line 2162 in f0c2329
I'm not familiar enough with the internals of protobuf to know whether the protobuf setup in utility.cc is correct, however it appears to be common from a quick scan through other code.
I'm also not sure if this line is specifically the issue, or its prior to this line in the cluster setup that is the problem.
Would really appreciate some guidance on how to troubleshoot this any further. Unfortunately this crash is highly memory dependent and doesn't occur from a main build, so this is reproducible only in my fork.
Call Stack:
This call stack is generated by watchpoint on raw_metadata_fetcher_
The text was updated successfully, but these errors were encountered: