High or critical vulnerabilities detected. Scan results are below:

{"SchemaVersion":2,"ArtifactName":"ghcr.io/kyverno/kyverno:release-1.10","ArtifactType":"container_image","Metadata":{"OS":{"Family":"alpine","Name":"3.19_rc1"},"ImageID":"sha256:c730195b31c2aac430adc953bbc381c8c3680140525b1f0a739b029beb958b1a","DiffIDs":["sha256:1c1cdd882e5e738c558650d7ec35254f227fd7a51371d521e76307aeeb018d95","sha256:ffe56a1c5f3878e9b5f803842adb9e2ce81584b6bd027e8599582aefe14a975b","sha256:a1f363336e4f15da526a86f52e6778ba06a549572397e8e9549179ec1cf94ca7"],"RepoTags":["ghcr.io/kyverno/kyverno:release-1.10"],"RepoDigests":["ghcr.io/kyverno/kyverno@sha256:5d390feead9fd709fca6a753dc7fffb6744d271875b2a825ba35cc1664b4b49e"],"ImageConfig":{"architecture":"amd64","author":"github.com/ko-build/ko","created":"2023-11-19T16:14:37Z","history":[{"author":"apko","created":"2023-11-19T16:14:37Z","created_by":"apko","comment":"This is an apko single-layer image"},{"author":"ko","created":"0001-01-01T00:00:00Z","created_by":"ko build ko://github.com/kyverno/kyverno/cmd/kyverno","comment":"kodata contents, at $KO_DATA_PATH"},{"author":"ko","created":"0001-01-01T00:00:00Z","created_by":"ko build ko://github.com/kyverno/kyverno/cmd/kyverno","comment":"go build output, at /ko-app/kyverno"}],"os":"linux","rootfs":{"type":"layers","diff_ids":["sha256:1c1cdd882e5e738c558650d7ec35254f227fd7a51371d521e76307aeeb018d95","sha256:ffe56a1c5f3878e9b5f803842adb9e2ce81584b6bd027e8599582aefe14a975b","sha256:a1f363336e4f15da526a86f52e6778ba06a549572397e8e9549179ec1cf94ca7"]},"config":{"Entrypoint":["/ko-app/kyverno"],"Env":["PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/ko-app","SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt","KO_DATA_PATH=/var/run/ko"],"User":"65532"}}},"Results":[{"Target":"ghcr.io/kyverno/kyverno:release-1.10 (alpine 3.19_rc1)","Class":"os-pkgs","Type":"alpine"},{"Target":"ko-app/kyverno","Class":"lang-pkgs","Type":"gobinary","Vulnerabilities":[{"VulnerabilityID":"CVE-2023-30551","PkgName":"github.com/sigstore/rekor","InstalledVersion":"v1.0.1","FixedVersion":"1.1.1","Status":"fixed","Layer":{"Digest":"sha256:5045e250f18fcf8b0c8d8ef912bb8c87734928489835fd8c08644cc98095abe7","DiffID":"sha256:a1f363336e4f15da526a86f52e6778ba06a549572397e8e9549179ec1cf94ca7"},"SeveritySource":"ghsa","PrimaryURL":"https://avd.aquasec.com/nvd/cve-2023-30551","DataSource":{"ID":"ghsa","Name":"GitHub Security Advisory Go","URL":"https://github.com/advisories?query=type%3Areviewed+ecosystem%3Ago"},"Title":"rekor: compressed archives can result in OOM conditions","Description":"Rekor is an open source software supply chain transparency log. Rekor prior to version 1.1.1 may crash due to out of memory (OOM) conditions caused by reading archive metadata files into memory without checking their sizes first. Verification of a JAR file submitted to Rekor can cause an out of memory crash if files within the META-INF directory of the JAR are sufficiently large. Parsing of an APK file submitted to Rekor can cause an out of memory crash if the .SIGN or .PKGINFO files within the APK are sufficiently large. The OOM crash has been patched in Rekor version 1.1.1. There are no known workarounds.","Severity":"HIGH","CweIDs":["CWE-770"],"CVSS":{"ghsa":{"V3Vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","V3Score":7.5},"nvd":{"V3Vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","V3Score":7.5},"redhat":{"V3Vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","V3Score":7.5}},"References":["https://access.redhat.com/security/cve/CVE-2023-30551","https://github.com/sigstore/rekor","https://github.com/sigstore/rekor/commit/cf42ace82667025fe128f7a50cf6b4cdff51cc48","https://github.com/sigstore/rekor/releases/tag/v1.1.1","https://github.com/sigstore/rekor/security/advisories/GHSA-2h5h-59f5-c5x9","https://nvd.nist.gov/vuln/detail/CVE-2023-30551","https://www.cve.org/CVERecord?id=CVE-2023-30551"],"PublishedDate":"2023-05-08T16:15:09.453Z","LastModifiedDate":"2023-05-12T16:27:55.07Z"},{"VulnerabilityID":"CVE-2023-45142","PkgName":"go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp","InstalledVersion":"v0.40.0","FixedVersion":"0.44.0","Status":"fixed","Layer":{"Digest":"sha256:5045e250f18fcf8b0c8d8ef912bb8c87734928489835fd8c08644cc98095abe7","DiffID":"sha256:a1f363336e4f15da526a86f52e6778ba06a549572397e8e9549179ec1cf94ca7"},"SeveritySource":"ghsa","PrimaryURL":"https://avd.aquasec.com/nvd/cve-2023-45142","DataSource":{"ID":"ghsa","Name":"GitHub Security Advisory Go","URL":"https://github.com/advisories?query=type%3Areviewed+ecosystem%3Ago"},"Title":"opentelemetry: DoS vulnerability in otelhttp","Description":"OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. A handler wrapper out of the box adds labels http.user_agent and http.method that have unbound cardinality. It leads to the server's potential memory exhaustion when many malicious requests are sent to it. HTTP header User-Agent or HTTP method for requests can be easily set by an attacker to be random and long. The library internally uses httpconv.ServerRequest that records every value for HTTP method and User-Agent. In order to be affected, a program has to use the otelhttp.NewHandler wrapper and not filter any unknown HTTP methods or User agents on the level of CDN, LB, previous middleware, etc. Version 0.44.0 fixed this issue when the values collected for attribute http.request.method were changed to be restricted to a set of well-known values and other high cardinality attributes were removed. As a workaround to stop being affected, otelhttp.WithFilter() can be used, but it requires manual careful configuration to not log certain requests entirely. For convenience and safe usage of this library, it should by default mark with the label unknown non-standard HTTP methods and User agents to show that such requests were made but do not increase cardinality. In case someone wants to stay with the current behavior, library API should allow to enable it.","Severity":"HIGH","CweIDs":["CWE-770"],"CVSS":{"ghsa":{"V3Vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","V3Score":7.5},"nvd":{"V3Vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","V3Score":7.5},"redhat":{"V3Vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","V3Score":7.5}},"References":["https://access.redhat.com/security/cve/CVE-2023-45142","https://github.com/advisories/GHSA-cg3q-j54f-5p7p","https://github.com/open-telemetry/opentelemetry-go-contrib","https://github.com/open-telemetry/opentelemetry-go-contrib/blob/5f7e6ad5a49b45df45f61a1deb29d7f1158032df/instrumentation/net/http/otelhttp/handler.go#L63-L65","https://github.com/open-telemetry/opentelemetry-go-contrib/pull/4277","https://github.com/open-telemetry/opentelemetry-go-contrib/releases/tag/v1.19.0","https://github.com/open-telemetry/opentelemetry-go-contrib/security/advisories/GHSA-5r5m-65gx-7vrh","https://github.com/open-telemetry/opentelemetry-go-contrib/security/advisories/GHSA-rcjv-mgp8-qvmr","https://github.com/open-telemetry/opentelemetry-go/blob/38e1b499c3da3107694ad2660b3888eee9c8b896/semconv/internal/v2/http.go#L223","https://github.com/open-telemetry/opentelemetry-go/blob/v1.12.0/semconv/internal/v2/http.go#L159","https://nvd.nist.gov/vuln/detail/CVE-2023-45142","https://www.cve.org/CVERecord?id=CVE-2023-45142"],"PublishedDate":"2023-10-12T17:15:09.99Z","LastModifiedDate":"2023-10-18T18:27:50.437Z"},{"VulnerabilityID":"GHSA-m425-mq94-257g","PkgName":"google.golang.org/grpc","InstalledVersion":"v1.54.0","FixedVersion":"1.56.3, 1.57.1, 1.58.3","Status":"fixed","Layer":{"Digest":"sha256:5045e250f18fcf8b0c8d8ef912bb8c87734928489835fd8c08644cc98095abe7","DiffID":"sha256:a1f363336e4f15da526a86f52e6778ba06a549572397e8e9549179ec1cf94ca7"},"SeveritySource":"ghsa","PrimaryURL":"https://github.com/advisories/GHSA-m425-mq94-257g","DataSource":{"ID":"ghsa","Name":"GitHub Security Advisory Go","URL":"https://github.com/advisories?query=type%3Areviewed+ecosystem%3Ago"},"Title":"gRPC-Go HTTP/2 Rapid Reset vulnerability","Description":"### Impact\nIn affected releases of gRPC-Go, it is possible for an attacker to send HTTP/2 requests, cancel them, and send subsequent requests, which is valid by the HTTP/2 protocol, but would cause the gRPC-Go server to launch more concurrent method handlers than the configured maximum stream limit.\n\n### Patches\nThis vulnerability was addressed by #6703 and has been included in patch releases: 1.56.3, 1.57.1, 1.58.3. It is also included in the latest release, 1.59.0.\n\nAlong with applying the patch, users should also ensure they are using the grpc.MaxConcurrentStreams server option to apply a limit to the server's resources used for any single connection.\n\n### Workarounds\nNone.\n\n### References\n#6703\n","Severity":"HIGH","CVSS":{"ghsa":{"V3Vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","V3Score":7.5}},"References":["https://github.com/grpc/grpc-go","https://github.com/grpc/grpc-go/commit/f2180b4d5403d2210b30b93098eb7da31c05c721","https://github.com/grpc/grpc-go/pull/6703","https://github.com/grpc/grpc-go/security/advisories/GHSA-m425-mq94-257g"]}]}]}