Setting CURLOPT_AWS_SIGV4 to NULL but does not disable SigV4 authentication,
contrary to expectations and documentation. A subsequent transfer on the same
handle still sends an Authorization: AWS4-HMAC-SHA256 header to whatever URL
isset next, leaking state information.
8.14.38.14.3Exploitability
AV:NAC:HPR:NUI:NScope
S:UImpact
C:HI:HA:H8.1/CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H