zen
commented
1 year ago Even internal AWS ECR scan shows the same. This should be fixed ASAP.
Open awsitcloudpro opened 1 year ago
zen
commented
1 year ago Even internal AWS ECR scan shows the same. This should be fixed ASAP.
ECR Clair scan of a Lambda docker image based on
public.ecr.aws/lambda/python:3shows the following vulnerabilities, all apparently in base AL2 image:.. CVE-2022-42915: A vulnerability was found in curl. The issue occurs if curl is told to use an HTTP proxy for a transfer with a non-HTTP(S) URL. It sets up the connection to the remote server by issuing aCONNECTrequest to the proxy and then tunnels the rest of the protocol through. An HTTP proxy might refuse this request (HTTP proxies often only allow outgoing connections to specific port numbers, like 443 for HTTPS) and instead return a non-200 response code to the client. Due to flaws in the error/cleanup handling, this could trigger a double-free issue in curl if using one of the following schemes in the URL for the transfer:dict,gopher,gophers,ldap,ldaps,rtmp,rtmps,telnet.CVE-2022-35260: A vulnerability was found in curl. The issue occurs when curl is told to parse a.netrcfile for credentials. If that file ends in a line with consecutive non-white space letters and no newline, curl could read past the end of the stack-based buffer, and if the read works, it can write a zero byte beyond its boundary. This issue, in most cases, causes a segfault or similar problem. A denial of service can occur if a malicious user can provide a custom netrc file to an application or otherwise affect its contents. CVE-2022-32221: A vulnerability was found in curl. The issue occurs when doing HTTP(S) transfers, where curl might erroneously use the read callback (CURLOPT_READFUNCTION) to ask for data to send, even when theCURLOPT_POSTFIELDSoption has been set if it previously used the same handle to issue aPUTrequest which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequentPOSTrequest... CVE-2022-42915: A vulnerability was found in curl. The issue occurs if curl is told to use an HTTP proxy for a transfer with a non-HTTP(S) URL. It sets up the connection to the remote server by issuing aCONNECTrequest to the proxy and then tunnels the rest of the protocol through. An HTTP proxy might refuse this request (HTTP proxies often only allow outgoing connections to specific port numbers, like 443 for HTTPS) and instead return a non-200 response code to the client. Due to flaws in the error/cleanup handling, this could trigger a double-free issue in curl if using one of the following schemes in the URL for the transfer:dict,gopher,gophers,ldap,ldaps,rtmp,rtmps,telnet.CVE-2022-35260: A vulnerability was found in curl. The issue occurs when curl is told to parse a.netrcfile for credentials. If that file ends in a line with consecutive non-white space letters and no newline, curl could read past the end of the stack-based buffer, and if the read works, it can write a zero byte beyond its boundary. This issue, in most cases, causes a segfault or similar problem. A denial of service can occur if a malicious user can provide a custom netrc file to an application or otherwise affect its contents. CVE-2022-32221: A vulnerability was found in curl. The issue occurs when doing HTTP(S) transfers, where curl might erroneously use the read callback (CURLOPT_READFUNCTION) to ask for data to send, even when theCURLOPT_POSTFIELDSoption has been set if it previously used the same handle to issue aPUTrequest which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequentPOSTrequest.