go-git is a highly extensible git implementation library written in pure Go. An argument injection vulnerability was discovered in go-git versions prior to v5.13. Successful exploitation of this vulnerability could allow an attacker to set arbitrary values to git-upload-pack flags. This only happens when the file transport protocol is being used, as that is the only protocol that shells out to git binaries. This vulnerability is fixed in 5.13.0.

go-git is a highly extensible git implementation library written in pure Go. A denial of service (DoS) vulnerability was discovered in go-git versions prior to v5.13. This vulnerability allows an attacker to perform denial of service attacks by providing specially crafted responses from a Git server which triggers resource exhaustion in go-git clients. Users running versions of go-git from v4 and above are recommended to upgrade to v5.13 in order to mitigate this vulnerability.

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/cry...@v0.31.0 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.

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

An issue was discovered in Cloud Native Computing Foundation (CNCF) Helm through 3.13.3. It displays values of secrets when the --dry-run flag is used. This is a security concern in some use cases, such as a --dry-run call by a CI/CD tool. NOTE: the vendor's position is that this behavior was introduced intentionally, and cannot be removed without breaking backwards compatibility (some users may be relying on these values). Also, it is not the Helm Project's responsibility if a user decides to use --dry-run within a CI/CD environment whose output is visible to unauthorized persons.

An attacker can pass a malicious malformed token which causes unexpected memory to be consumed during parsing.

Due to the usage of a variable time instruction in the assembly implementation of an internal function, a small number of bits of secret scalars are leaked on the ppc64le architecture. Due to the way this function is used, we do not believe this leakage is enough to allow recovery of the private key when P-256 is used in any well known protocols.

Uncontrolled recursion in Decoder.Decode in encoding/gob before Go 1.17.12 and Go 1.18.4 allows an attacker to cause a panic due to stack exhaustion via a message which contains deeply nested structures.

Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.

Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion.

A SMB force-authentication vulnerability exists in all versions of OPA for Windows prior to v0.68.0. The vulnerability exists because of improper input validation, allowing a user to pass an arbitrary SMB share instead of a Rego file as an argument to OPA CLI or to one of the OPA Go library’s functions.

An attacker can craft an input to the Parse functions that would be processed non-linearly with respect to its length, resulting in extremely slow parsing. This could cause a denial of service.

containerd is an open-source container runtime. A bug was found in containerd prior to versions 1.6.38, 1.7.27, and 2.0.4 where containers launched with a User set as a `UID:GID` larger than the maximum 32-bit signed integer can cause an overflow condition where the container ultimately runs as root (UID 0). This could cause unexpected behavior for environments that require containers to run as a non-root user. This bug has been fixed in containerd 1.6.38, 1.7.27, and 2.04. As a workaround, ensure that only trusted images are used and that only trusted users have permissions to import images.

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.

Controlled by an Kubernetes Operator. Asset ghcr.io/l3montree-dev/devguard-operator

ghcr.io/l3montree-dev/devguard-operator

main

Devguard-Pipeline

quay.io/jetstack/cert-manager-acmesolver

ghcr.io/l3montree-dev/devguard-postgresql

devguard-action

ghcr.io/l3montree-dev/devguard

docker.io/oryd/kratos

 Devguard-Pipeline

devguard-web

DevGuard Operator

devguard-scanner

devguard-documentation

Devguard Postgresql

devguard

Devguard

Robot User

OpenCoDE

Lars Hermges

Patrick Rissmann

Sebastian Kawelke

Tim Bastin

Refaei Shikho

Frédéric Noppe

refoo0

l3montree-robot

timbastin

seb-kw

devguard-bot-dev[bot]

L3montree Cybersecurity

Controlled by an Kubernetes Operator. Asset ghcr.io/l3montree-dev/devguard-postgresql

Controlled by an Kubernetes Operator. Asset ghcr.io/l3montree-dev/devguard

Controlled by an Kubernetes Operator. Asset docker.io/oryd/kratos

This is a scan for Devguard CI/CD components in a GitLab project, aimed at testing whether these components function correctly.

The scanner component of the devguard project

The documentation for the DevGuard Project

Manage your CVEs seamlessly, Integrate your Vulnerability Scanners, Documentation made easy, Compliance to security Frameworks - OWASP Incubating Project

Package	Max Risk	Total Risk	Flaw Count	Installed Version	Action
github.com/go-git/go-git/v5	4.5	8.0	2	5.12.0	Update to version 5.13.0 to reduce total risk by 8.0
golang.org/x/crypto	4.3	7.8	2	0.28.0	Update to version 0.35.0 to reduce total risk by 7.8
golang.org/x/crypto	4.3	7.8	2	0.25.0	Update to version 0.35.0 to reduce total risk by 7.8
helm.sh/helm/v3	4.2	4.2	1	3.15.3	No fix available
golang.org/x/oauth2	3.5	3.5	1	0.20.0	Update to version 0.27.0 to reduce total risk by 3.5
stdlib	3.5	8.9	6	1.22.5	Update to version 1.22.7 to reduce total risk by 8.9
golang.org/x/oauth2	3.5	3.5	1	0.23.0	Update to version 0.27.0 to reduce total risk by 3.5
github.com/open-policy-agent/opa	2.8	2.8	1	0.66.0	Update to version 0.68.0 to reduce total risk by 2.8
golang.org/x/net	2.5	2.5	2	0.27.0	Update to version 0.36.0 to reduce total risk by 2.5
golang.org/x/net	2.5	2.5	2	0.29.0	Update to version 0.36.0 to reduce total risk by 2.5
github.com/containerd/containerd	2.1	2.1	1	1.7.13	Update to version 1.7.27 to reduce total risk by 2.1
github.com/containerd/containerd	2.1	2.1	1	1.7.20	Update to version 1.7.27 to reduce total risk by 2.1
github.com/golang-jwt/jwt/v4	1.4	1.4	1	4.5.0	Update to version 4.5.1 to reduce total risk by 1.4
stdlib	0.0	0.0	3	1.23.4	Update to version 1.23.6 to reduce total risk by 0.0

L3montree Cybersecurity
Organization
/Devguard
Project
/ghcr.io/l3montree-dev/devguard-operator
Asset

Identified Risks