github.com/kyverno/kyverno-v1.12.5: 6 vulnerabilities (highest severity is: 7.4)

[mend-bolt-for-github]

Vulnerable Library - github.com/kyverno/kyverno-v1.12.5

Library home page: https://proxy.golang.org/github.com/kyverno/kyverno/@v/v1.12.5.zip

Path to dependency file: /go.mod

Path to vulnerable library: /go/pkg/mod/cache/download/github.com/kyverno/kyverno/@v/v1.12.5.mod

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (github.com/kyverno/kyverno-v1.12.5 version)	Remediation Possible**
CVE-2024-45337	High	7.4	golang.org/x/crypto-v0.28.0	Transitive	N/A*	❌
CVE-2024-36620	Medium	6.5	github.com/Docker/Docker-v25.0.5+incompatible	Transitive	N/A*	❌
CVE-2024-6531	Medium	6.4	github.com/open-Policy-agent/opa-v0.63.0	Transitive	N/A*	❌
CVE-2024-51744	Low	3.1	github.com/golang-JWT/jwt/v4-v4.5.0	Transitive	N/A*	❌
CVE-2024-48921	Low	2.7	github.com/kyverno/kyverno-v1.12.5	Direct	github.com/kyverno/kyverno-v1.13.0	❌
CVE-2024-47534	Low	0.0	github.com/theupdateframework/go-tuf-v0.7.0	Transitive	N/A*	❌

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2024-45337

Vulnerable Library - golang.org/x/crypto-v0.28.0

Library home page: https://proxy.golang.org/golang.org/x/crypto/@v/v0.28.0.zip

Path to dependency file: /go.mod

Path to vulnerable library: /go/pkg/mod/cache/download/golang.org/x/crypto/@v/v0.28.0.mod

Dependency Hierarchy:

• github.com/kyverno/kyverno-v1.12.5 (Root Library)
  • github.com/sigstore/k8s-manifest-sigstore-v0.5.4
    • github.com/Protonmail/go-crypto-v1.0.0
      • ❌ golang.org/x/crypto-v0.28.0 (Vulnerable Library)

Found in base branch: main

Vulnerability Details

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key. Since this API is widely misused, as a partial mitigation golang.org/x/[email protected] enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth. Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

Publish Date: 2024-12-11

URL: CVE-2024-45337

CVSS 3 Score Details (7.4)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-v778-237x-gjrc

Release Date: 2024-12-11

Fix Resolution: golang.org/x/crypto-v0.31.0

Step up your Open Source Security Game with Mend here

CVE-2024-36620

Vulnerable Library - github.com/Docker/Docker-v25.0.5+incompatible

Moby Project - a collaborative project for the container ecosystem to assemble container-based systems

Library home page: https://proxy.golang.org/github.com/!docker/!docker/@v/v25.0.5+incompatible.zip

Path to dependency file: /go.mod

Path to vulnerable library: /go/pkg/mod/cache/download/github.com/docker/docker/@v/v25.0.5+incompatible.mod

Dependency Hierarchy:

• github.com/kyverno/kyverno-v1.12.5 (Root Library)
  • github.com/sigstore/k8s-manifest-sigstore-v0.5.4
    • github.com/Google/go-containerregistry-v0.19.1
      • github.com/Docker/cli-v25.0.1+incompatible
        • ❌ github.com/Docker/Docker-v25.0.5+incompatible (Vulnerable Library)

Found in base branch: main

Vulnerability Details

moby v25.0.0 - v26.0.2 is vulnerable to NULL Pointer Dereference via daemon/images/image_history.go.

Publish Date: 2024-11-29

URL: CVE-2024-36620

CVSS 3 Score Details (6.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: Low
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-q59j-vv4j-v33c

Release Date: 2024-11-29

Fix Resolution: github.com/moby/moby-v26.1.0

Step up your Open Source Security Game with Mend here

CVE-2024-6531

Vulnerable Library - github.com/open-Policy-agent/opa-v0.63.0

Open Policy Agent (OPA) is an open source, general-purpose policy engine.

Library home page: https://proxy.golang.org/github.com/open-!policy-agent/opa/@v/v0.63.0.zip

Path to dependency file: /go.mod

Path to vulnerable library: /go/pkg/mod/cache/download/github.com/open-policy-agent/opa/@v/v0.63.0.mod

Dependency Hierarchy:

• github.com/kyverno/kyverno-v1.12.5 (Root Library)
  • github.com/sigstore/k8s-manifest-sigstore-v0.5.4
    • github.com/sigstore/cosign/v2-v2.2.4
      • ❌ github.com/open-Policy-agent/opa-v0.63.0 (Vulnerable Library)

Found in base branch: main

Vulnerability Details

A vulnerability has been identified in Bootstrap that exposes users to Cross-Site Scripting (XSS) attacks. The issue is present in the carousel component, where the data-slide and data-slide-to attributes can be exploited through the href attribute of an tag due to inadequate sanitization. This vulnerability could potentially enable attackers to execute arbitrary JavaScript within the victim's browser.

Publish Date: 2024-07-11

URL: CVE-2024-6531

CVSS 3 Score Details (6.4)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: Low
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-vc8w-jr9v-vj7f

Release Date: 2024-07-11

Fix Resolution: bootstrap - 5.0.0

Step up your Open Source Security Game with Mend here

CVE-2024-51744

Vulnerable Library - github.com/golang-JWT/jwt/v4-v4.5.0

Library home page: https://proxy.golang.org/github.com/golang-!j!w!t/jwt/v4/@v/v4.5.0.zip

Path to dependency file: /go.mod

Path to vulnerable library: /go/pkg/mod/cache/download/github.com/golang-jwt/jwt/v4/@v/v4.5.0.mod

Dependency Hierarchy:

• github.com/kyverno/kyverno-v1.12.5 (Root Library)
  • github.com/sigstore/k8s-manifest-sigstore-v0.5.4
    • github.com/sigstore/cosign/v2-v2.2.4
      • github.com/chrismellard/docker-credential-acr-env-v0.0.0-20230304212654-82a0ddb27589
        • github.com/Azure/go-autorest/autorest/adal-v0.9.23
          • ❌ github.com/golang-JWT/jwt/v4-v4.5.0 (Vulnerable Library)

Found in base branch: main

Vulnerability Details

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 function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above.

Publish Date: 2024-11-04

URL: CVE-2024-51744

CVSS 3 Score Details (3.1)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-29wx-vh33-7x7r

Release Date: 2024-11-04

Fix Resolution: github.com/golang-jwt/jwt-v4.5.1

Step up your Open Source Security Game with Mend here

CVE-2024-48921

Vulnerable Library - github.com/kyverno/kyverno-v1.12.5

Library home page: https://proxy.golang.org/github.com/kyverno/kyverno/@v/v1.12.5.zip

Path to dependency file: /go.mod

Path to vulnerable library: /go/pkg/mod/cache/download/github.com/kyverno/kyverno/@v/v1.12.5.mod

Dependency Hierarchy:

• ❌ github.com/kyverno/kyverno-v1.12.5 (Vulnerable Library)

Found in base branch: main

Vulnerability Details

Kyverno is a policy engine designed for Kubernetes. A kyverno ClusterPolicy, ie. "disallow-privileged-containers," can be overridden by the creation of a PolicyException in a random namespace. By design, PolicyExceptions are consumed from any namespace. Administrators may not recognize that this allows users with privileges to non-kyverno namespaces to create exceptions. This vulnerability is fixed in 1.13.0.

Publish Date: 2024-10-29

URL: CVE-2024-48921

CVSS 3 Score Details (2.7)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: High
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: Low
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-qjvc-p88j-j9rm

Release Date: 2024-10-29

Fix Resolution: github.com/kyverno/kyverno-v1.13.0

Step up your Open Source Security Game with Mend here

CVE-2024-47534

Vulnerable Library - github.com/theupdateframework/go-tuf-v0.7.0

Library home page: https://proxy.golang.org/github.com/theupdateframework/go-tuf/@v/v0.7.0.zip

Path to dependency file: /go.mod

Path to vulnerable library: /go/pkg/mod/cache/download/github.com/theupdateframework/go-tuf/@v/v0.7.0.mod

Dependency Hierarchy:

• github.com/kyverno/kyverno-v1.12.5 (Root Library)
  • github.com/sigstore/k8s-manifest-sigstore-v0.5.4
    • github.com/SigStore/rekor-v1.3.6
      • ❌ github.com/theupdateframework/go-tuf-v0.7.0 (Vulnerable Library)

Found in base branch: main

Vulnerability Details

go-tuf is a Go implementation of The Update Framework (TUF). The go-tuf client inconsistently traces the delegations. For example, if targets delegate to "A", and to "B", and "B" delegates to "C", then the client should trace the delegations in the order "A" then "B" then "C" but it may incorrectly trace the delegations "B"->"C"->"A". This vulnerability is fixed in 2.0.1.

Publish Date: 2024-10-01

URL: CVE-2024-47534

CVSS 3 Score Details (0.0)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-4f8r-qqr9-fq8j

Release Date: 2024-10-01

Fix Resolution: theupdateframework/go-tuf-v2.0.1

Step up your Open Source Security Game with Mend here

[mend-bolt-for-github]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-bolt-for-github]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.