SIGSEGV when execute AWSAuthV4Signer::GenerateSignature

[Userwhite]

Describe the bug

use 1.11.267, meet a SIGSEGV problem when we try to put object

*** Aborted at 1753910420 (unix time) try "date -d @1753910420" if you are using GNU date ***
PC: @          0x839531f SHA256_Update
*** SIGSEGV (@0x20) received by PID 22097 (TID 0x7f56913ff700) from PID 32; stack trace: ***
    @     0x7f8228b35997 __pthread_once_slow
    @          0x7d8fb40 google::(anonymous namespace)::FailureSignalHandler(int, siginfo_t*, void*)
    @     0x7f8228b38730 (/usr/lib/x86_64-linux-gnu/libpthread-2.28.so+0x1272f)
    @          0x839531f SHA256_Update
    @          0x83434e0 HMAC_Final
    @          0x77e5554 Aws::Utils::Crypto::Sha256HMACOpenSSLImpl::Calculate(Aws::Utils::Array<unsigned char> const&, Aws::Utils::Array<unsigned char> const&)
    @          0x7881048 Aws::Utils::Crypto::Sha256HMAC::Calculate(Aws::Utils::Array<unsigned char> const&, Aws::Utils::Array<unsigned char> const&) [clone .localalias]
    @          0x77f3b30 Aws::Client::AWSAuthV4Signer::GenerateSignature(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, Aws::Utils::Array<unsigned char> const&) const
    @          0x77f7844 Aws::Client::AWSAuthV4Signer::GenerateSignature(Aws::Auth::AWSCredentials const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&
    @          0x7831580 Aws::Client::AWSAuthV4Signer::SignRequest(Aws::Http::HttpRequest&, char const*, char const*, bool) const
    @          0x783ef29 bool smithy::components::tracing::TracingUtils::MakeCallWithTiming<bool>(std::function<bool ()>, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, smithy::components::tracing::Meter const&, std::map<std::__cxx11::basic
    @          0x781a3fa Aws::Client::AWSClient::AttemptOneRequest(std::shared_ptr<Aws::Http::HttpRequest> const&, Aws::AmazonWebServiceRequest const&, char const*, char const*, char const*) const
    @          0x78229ec Aws::Client::AWSClient::AttemptExhaustively(Aws::Http::URI const&, Aws::AmazonWebServiceRequest const&, Aws::Http::HttpMethod, char const*, char const*, char const*) const
    @          0x7826096 Aws::Client::AWSXMLClient::MakeRequest(Aws::Http::URI const&, Aws::AmazonWebServiceRequest const&, Aws::Http::HttpMethod, char const*, char const*, char const*) const
    @          0x7826d9e Aws::Client::AWSXMLClient::MakeRequest(Aws::AmazonWebServiceRequest const&, Aws::Endpoint::AWSEndpoint const&, Aws::Http::HttpMethod, char const*, char const*, char const*) const
    @          0x7713d5c Aws::S3::S3Client::PutObject(Aws::S3::Model::PutObjectRequest const&) const::{lambda()#1}::operator()() const
    @          0x7713f05 std::_Function_handler<Aws::Utils::Outcome<Aws::S3::Model::PutObjectResult, Aws::S3::S3Error> (), Aws::S3::S3Client::PutObject(Aws::S3::Model::PutObjectRequest const&) const::{lambda()#1}>::_M_invoke(std::_Any_data const&)
    @          0x77bf2f6 Aws::Utils::Outcome<Aws::S3::Model::PutObjectResult, Aws::S3::S3Error> smithy::components::tracing::TracingUtils::MakeCallWithTiming<Aws::Utils::Outcome<Aws::S3::Model::PutObjectResult, Aws::S3::S3Error> >(std::function<Aws::Utils::Outcome<Aws::S3::Model::
    @          0x772728d Aws::S3::S3Client::PutObject(Aws::S3::Model::PutObjectRequest const&) const

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

progress running normally

Current Behavior

progress somtimes meet SIGSEGV problem

Reproduction Steps

can't reproduce stably

Possible Solution

No response

Additional Information/Context

No response

AWS CPP SDK version used

1.11.267

Compiler and Version used

gcc (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0

Operating System and version

Debian GNU/Linux 10 (buster)

[sbiscigl]

Reproduction Steps
can't reproduce stably

we really need a reproducible case to diagnose

AWS CPP SDK version used
1.11.267

does the issue exist on the latest version?

[Userwhite]

Do you meet the same stacktrace? we only find two cases in recent 3 month, and only know it's a put request for write data.
The cost of upgrade is high because we use it in one database, so I don't know if upgrade works.

[sbiscigl]

we only find two cases in recent 3 month,

We cant investigate on speculation we need a reproduction example to investigate something, there are too many unknowns about your environment and your build and your usage. We need an example to debug further.

The cost of upgrade is high because we use it in one database, so I don't know if upgrade works.

That version is over a year old Feb 16, 2024, even if there is a problem we would only push a fix to the latest version. I would highly suggest moving to the latest version to pick up bug fixes

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than a week. We encourage you to check if this is still an issue in the latest release. Because it has been longer than a week since the last update on this, and in the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or add an upvote to prevent automatic closure, or if the issue is already closed, please feel free to open a new one.