You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*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
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. In versions on the 4.x branch prior to version 4.0.5, when parsing compact JWS or JWE input, Go JOSE could use excessive memory. The code used strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of "." characters. An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service. Version 4.0.5 fixes this issue. As a workaround, applications could pre-validate that payloads passed to Go JOSE do not contain an excessive number of "." characters.
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.
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.
The go-jose package before 3.0.1 is subject to a "billion hashes attack" causing denial-of-service when decrypting JWE inputs. This occurs when an attacker can provide a PBES2 encrypted JWE blob with a very large p2c value that, when decrypted, produces a denial-of-service.
Path to vulnerable library: /go/pkg/mod/cache/download/github.com/hashicorp/go-retryablehttp/@v/v0.7.4.mod,/go/pkg/mod/cache/download/github.com/hashicorp/go-retryablehttp/@v/v0.7.4.mod
go-retryablehttp prior to 0.7.7 did not sanitize urls when writing them to its log file. This could lead to go-retryablehttp writing sensitive HTTP basic auth credentials to its log file. This vulnerability, CVE-2024-6104, was fixed in go-retryablehttp 0.7.7.
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.
In Go net/http, x/net/proxy, x/net/http/httpproxy there is a proxy bypass vulnerability using IPv6 zone IDs. Matching of hosts against proxy patterns could improperly treat an IPv6 zone ID
as a hostname component. For example, when the NO_PROXY environment variable was
set to "*.example.com", a request to "[::1%25.example.com]:80` would incorrectly
match and not be proxied. This affects versions before 1.23.7 and 1.24.x before 1.24.1.
Package jose aims to provide an implementation of the Javascript Object Signing and Encryption set of standards. An attacker could send a JWE containing compressed data that used large amounts of memory and CPU when decompressed by Decrypt or DecryptMulti. Those functions now return an error if the decompressed data would exceed 250kB or 10x the compressed size (whichever is larger). This vulnerability has been patched in versions 4.0.1, 3.0.3 and 2.6.3.
mend-bolt-for-githubbot
changed the title
github.com/intelops/go-common-v1.0.20: 1 vulnerabilities (highest severity is: 6.5)
github.com/intelops/go-common-v1.0.20: 2 vulnerabilities (highest severity is: 6.5)
Apr 23, 2024
mend-bolt-for-githubbot
changed the title
github.com/intelops/go-common-v1.0.20: 2 vulnerabilities (highest severity is: 6.5)
github.com/intelops/go-common-v1.0.20: 3 vulnerabilities (highest severity is: 6.5)
Aug 11, 2024
mend-bolt-for-githubbot
changed the title
github.com/intelops/go-common-v1.0.20: 3 vulnerabilities (highest severity is: 6.5)
github.com/intelops/go-common-v1.0.20: 5 vulnerabilities (highest severity is: 7.4)
Feb 3, 2025
mend-bolt-for-githubbot
changed the title
github.com/intelops/go-common-v1.0.20: 5 vulnerabilities (highest severity is: 7.4)
github.com/intelops/go-common-v1.0.20: 6 vulnerabilities (highest severity is: 7.5)
Feb 25, 2025
mend-bolt-for-githubbot
changed the title
github.com/intelops/go-common-v1.0.20: 6 vulnerabilities (highest severity is: 7.5)
github.com/intelops/go-common-v1.0.20: 7 vulnerabilities (highest severity is: 7.5)
Feb 26, 2025
mend-bolt-for-githubbot
changed the title
github.com/intelops/go-common-v1.0.20: 7 vulnerabilities (highest severity is: 7.5)
github.com/intelops/go-common-v1.0.20: 8 vulnerabilities (highest severity is: 7.5)
Mar 9, 2025
Path to dependency file: /server/go.mod
Path to vulnerable library: /go/pkg/mod/cache/download/golang.org/x/crypto/@v/v0.22.0.mod
Vulnerabilities
*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
Vulnerable Library - github.com/go-jose/go-jose/v3-v3.0.0
An implementation of JOSE standards (JWE, JWS, JWT) in Go
Library home page: https://proxy.golang.org/github.com/go-jose/go-jose/v3/@v/v3.0.0.zip
Path to dependency file: /server/go.mod
Path to vulnerable library: /go/pkg/mod/cache/download/github.com/go-jose/go-jose/v3/@v/v3.0.0.mod
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
Go JOSE provides an implementation of the Javascript Object Signing and Encryption set of standards in Go, including support for JSON Web Encryption (JWE), JSON Web Signature (JWS), and JSON Web Token (JWT) standards. In versions on the 4.x branch prior to version 4.0.5, when parsing compact JWS or JWE input, Go JOSE could use excessive memory. The code used strings.Split(token, ".") to split JWT tokens, which is vulnerable to excessive memory consumption when processing maliciously crafted tokens with a large number of "." characters. An attacker could exploit this by sending numerous malformed tokens, leading to memory exhaustion and a Denial of Service. Version 4.0.5 fixes this issue. As a workaround, applications could pre-validate that payloads passed to Go JOSE do not contain an excessive number of "." characters.
Publish Date: 2025-02-24
URL: CVE-2025-27144
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-c6gw-w398-hv78
Release Date: 2025-02-24
Fix Resolution: v4.0.5
Step up your Open Source Security Game with Mend here
Vulnerable Library - golang.org/x/crypto-v0.22.0
Library home page: https://proxy.golang.org/golang.org/x/crypto/@v/v0.22.0.zip
Path to dependency file: /server/go.mod
Path to vulnerable library: /go/pkg/mod/cache/download/golang.org/x/crypto/@v/v0.22.0.mod
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
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.
Publish Date: 2025-02-26
URL: CVE-2025-22869
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://pkg.go.dev/vuln/GO-2025-3487
Release Date: 2025-02-26
Fix Resolution: v0.35.0
Step up your Open Source Security Game with Mend here
Vulnerable Library - golang.org/x/crypto-v0.22.0
Library home page: https://proxy.golang.org/golang.org/x/crypto/@v/v0.22.0.zip
Path to dependency file: /server/go.mod
Path to vulnerable library: /go/pkg/mod/cache/download/golang.org/x/crypto/@v/v0.22.0.mod
Dependency Hierarchy:
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:
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
Vulnerable Library - github.com/go-jose/go-jose/v3-v3.0.0
An implementation of JOSE standards (JWE, JWS, JWT) in Go
Library home page: https://proxy.golang.org/github.com/go-jose/go-jose/v3/@v/v3.0.0.zip
Path to dependency file: /server/go.mod
Path to vulnerable library: /go/pkg/mod/cache/download/github.com/go-jose/go-jose/v3/@v/v3.0.0.mod
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
The go-jose package before 3.0.1 is subject to a "billion hashes attack" causing denial-of-service when decrypting JWE inputs. This occurs when an attacker can provide a PBES2 encrypted JWE blob with a very large p2c value that, when decrypted, produces a denial-of-service.
Publish Date: 2023-11-22
URL: WS-2023-0431
CVSS 3 Score Details (6.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-2c7c-3mj9-8fqh
Release Date: 2023-11-22
Fix Resolution: v3.0.1
Step up your Open Source Security Game with Mend here
Vulnerable Library - github.com/hashiCorp/go-retryablehttp-v0.7.4
Library home page: https://proxy.golang.org/github.com/hashi!corp/go-retryablehttp/@v/v0.7.4.zip
Path to dependency file: /server/go.mod
Path to vulnerable library: /go/pkg/mod/cache/download/github.com/hashicorp/go-retryablehttp/@v/v0.7.4.mod,/go/pkg/mod/cache/download/github.com/hashicorp/go-retryablehttp/@v/v0.7.4.mod
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
go-retryablehttp prior to 0.7.7 did not sanitize urls when writing them to its log file. This could lead to go-retryablehttp writing sensitive HTTP basic auth credentials to its log file. This vulnerability, CVE-2024-6104, was fixed in go-retryablehttp 0.7.7.
Publish Date: 2024-06-24
URL: CVE-2024-6104
CVSS 3 Score Details (6.0)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2024-6104
Release Date: 2024-06-24
Fix Resolution: github.com/hashicorp/go-retryablehttp-v0.7.7
Step up your Open Source Security Game with Mend here
Vulnerable Library - golang.org/x/net-v0.24.0
Library home page: https://proxy.golang.org/golang.org/x/net/@v/v0.24.0.zip
Path to dependency file: /server/go.mod
Path to vulnerable library: /go/pkg/mod/cache/download/golang.org/x/net/@v/v0.24.0.mod
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
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.
Publish Date: 2024-12-18
URL: CVE-2024-45338
CVSS 3 Score Details (5.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Release Date: 2024-12-18
Fix Resolution: github.com/golang/net-v0.33.0
Step up your Open Source Security Game with Mend here
Vulnerable Library - golang.org/x/net-v0.24.0
Library home page: https://proxy.golang.org/golang.org/x/net/@v/v0.24.0.zip
Path to dependency file: /server/go.mod
Path to vulnerable library: /go/pkg/mod/cache/download/golang.org/x/net/@v/v0.24.0.mod
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
In Go net/http, x/net/proxy, x/net/http/httpproxy there is a proxy bypass vulnerability using IPv6 zone IDs. Matching of hosts against proxy patterns could improperly treat an IPv6 zone ID
as a hostname component. For example, when the NO_PROXY environment variable was
set to "*.example.com", a request to "[::1%25.example.com]:80` would incorrectly
match and not be proxied. This affects versions before 1.23.7 and 1.24.x before 1.24.1.
Publish Date: 2025-03-12
URL: CVE-2025-22870
CVSS 3 Score Details (4.4)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-qxp5-gwg8-xv66
Release Date: 2025-03-12
Fix Resolution: 0.36.0
Step up your Open Source Security Game with Mend here
Vulnerable Library - github.com/go-jose/go-jose/v3-v3.0.0
An implementation of JOSE standards (JWE, JWS, JWT) in Go
Library home page: https://proxy.golang.org/github.com/go-jose/go-jose/v3/@v/v3.0.0.zip
Path to dependency file: /server/go.mod
Path to vulnerable library: /go/pkg/mod/cache/download/github.com/go-jose/go-jose/v3/@v/v3.0.0.mod
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
Package jose aims to provide an implementation of the Javascript Object Signing and Encryption set of standards. An attacker could send a JWE containing compressed data that used large amounts of memory and CPU when decompressed by Decrypt or DecryptMulti. Those functions now return an error if the decompressed data would exceed 250kB or 10x the compressed size (whichever is larger). This vulnerability has been patched in versions 4.0.1, 3.0.3 and 2.6.3.
Publish Date: 2024-03-09
URL: CVE-2024-28180
CVSS 3 Score Details (4.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://www.cve.org/CVERecord?id=CVE-2024-28180
Release Date: 2024-03-09
Fix Resolution: v2.6.3,v3.0.3,v4.0.1
Step up your Open Source Security Game with Mend here
The text was updated successfully, but these errors were encountered: