Vulnerability #13
nrwiersmaAnnotations
10 errors and 1 warning
|
govulncheck
resource.SetDataKeys calls schema.ResourceData.Set, which eventually calls template.Template.Funcs
|
|
govulncheck
schema.realMain calls fmt.Fprintf, which eventually calls template.Error.Error
|
|
govulncheck
schema.realMain calls fmt.Fprintf, which eventually calls x509.Certificate.Verify
|
|
govulncheck
provider.lazyTokenSource.Token calls oauth2.reuseTokenSource.Token, which eventually calls tls.Dialer.DialContext
|
|
govulncheck
schema.realMain calls fmt.Fprintf, which calls tls.Conn.Write
|
|
govulncheck
provider.lazyTokenSource.Token calls oauth2.reuseTokenSource.Token, which eventually calls tls.Conn.Read
|
|
govulncheck
provider.lazyTokenSource.Token calls oauth2.reuseTokenSource.Token, which eventually calls tls.Conn.HandshakeContext
|
|
govulncheck
terraform.main calls plugin.Serve, which eventually calls tls.Conn.Handshake
|
|
govulncheck
schema.realMain calls fmt.Fprintf, which eventually calls x509.Certificate.Verify
|
|
govulncheck
schema.realMain calls fmt.Fprintf, which eventually calls x509.Certificate.Verify
|
|
govulncheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5, extractions/netrc@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|