### Terraform Version ```shell 1.9.8 ``` ### Terraform Configuration Files - ### Debug Output - ### Expected Behavior AWS Security Inspector (or other tool) don't reported CVE vulnerabilities ### Actual Behavior AWS Security Inspector findings CVE vulnerabilities in additional libraries ### Steps to Reproduce 1. add terraform package to Dockerfile 2. build image 3. push image to AWS ECR ### Additional Context CVE-2024-10006 - github.com/hashicorp/consul/api CVE-2024-10005 - github.com/hashicorp/consul/api A vulnerability was identified in Consul and Consul Enterprise (“Consul”) such that using Headers in L7 traffic intentions could bypass HTTP header based access rules. Installed version: v1.13.0 Fixed version: 1.20.1 CVE-2024-51744 - github.com/golang-jwt/jwt/v4 golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established func Installed version: v4.4.2 Fixed version: v4.5.1 ### References _No response_