github.com/grafana/grafana-v0.0.0: 8 vulnerabilities (highest severity is: 9.8) #22
Labels
Mend: dependency security vulnerability
Security vulnerability detected by Mend
Comments
mend-for-github-com
bot
added
the
Mend: dependency security vulnerability
mend-for-github-com
bot
changed the title
mend-for-github-com
bot
changed the title
mend-for-github-com
bot
changed the title
mend-for-github-com
bot
changed the title
mend-for-github-com
bot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Path to dependency file: /go.work
Path to vulnerable library: /home/wss-scanner/go/pkg/mod/cache/download/golang.org/x/net/@v/v0.28.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 - filippo.io/age-v1.1.1
Library home page: https://proxy.golang.org/filippo.io/age/@v/v1.1.1.zip
Path to dependency file: /go.work
Path to vulnerable library: /home/wss-scanner/go/pkg/mod/cache/download/filippo.io/age/@v/v1.1.1.mod
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
pyrage is a set of Python bindings for the rage file encryption library (age in Rust). "pyrage" uses the Rust "age" crate for its underlying operations, and "age" is vulnerable to GHSA-4fg7-vxc8-qx5w. All details of GHSA-4fg7-vxc8-qx5w are relevant to "pyrage" for the versions specified in this advisory. See GHSA-4fg7-vxc8-qx5w for full details. Versions of "pyrage" before 1.2.0 lack plugin support and are therefore not affected. An equivalent issue was fixed in "the reference Go implementation of age" (https://github.com/FiloSottile/age), see advisory GHSA-32gq-x56h-299c. This issue has been addressed in version 1.2.3 and all users are advised to update. There are no known workarounds for this vulnerability.
Publish Date: 2024-12-19
URL: CVE-2024-56327
CVSS 3 Score Details (9.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-32gq-x56h-299c
Release Date: 2024-12-19
Fix Resolution: github.com/FiloSottile/age-v1.2.1, age - 0.6.1, 0.7.2, 0.8.2, 0.9.3, 0.10.1, 0.11.1, rage - 0.6.1, 0.7.2, 0.8.2, 0.9.3, 0.10.1, 0.11.1
Vulnerable Library - github.com/openfga/openfga-v1.5.4
Library home page: https://proxy.golang.org/github.com/openfga/openfga/@v/v1.5.4.zip
Path to dependency file: /go.work
Path to vulnerable library: /home/wss-scanner/go/pkg/mod/cache/download/github.com/openfga/openfga/@v/v1.5.4.mod
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
OpenFGA is an authorization/permission engine. IN OpenFGA v1.3.8 to v1.8.2 (Helm chart openfga-0.1.38 to openfga-0.2.19, docker v1.3.8 to v.1.8.2) are vulnerable to authorization bypass under the following conditions: 1. calling Check API or ListObjects with a model that uses "conditions" (https://openfga.dev/docs/modeling/conditions), and 2. calling Check API or ListObjects API with "contextual tuples" (https://openfga.dev/docs/concepts#what-are-contextual-tuples) that include conditions and 3. OpenFGA is configured with caching enabled ("OPENFGA_CHECK_QUERY_CACHE_ENABLED"). Users are advised to upgrade to v1.8.3. There are no known workarounds for this vulnerability.
Publish Date: 2025-01-13
URL: CVE-2024-56323
CVSS 3 Score Details (8.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Origin: GHSA-32q6-rr98-cjqv
Release Date: 2025-01-13
Fix Resolution: v1.8.3
Vulnerable Library - golang.org/x/crypto-v0.26.0
Library home page: https://proxy.golang.org/golang.org/x/crypto/@v/v0.26.0.zip
Path to dependency file: /go.work
Path to vulnerable library: /home/wss-scanner/go/pkg/mod/cache/download/golang.org/x/crypto/@v/v0.26.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:
- 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
Vulnerable Library - github.com/golang/glog-v1.2.1
Leveled execution logs for Go
Library home page: https://proxy.golang.org/github.com/golang/glog/@v/v1.2.1.zip
Path to dependency file: /go.work
Path to vulnerable library: /home/wss-scanner/go/pkg/mod/cache/download/github.com/golang/glog/@v/v1.2.1.mod
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
When logs are written to a widely-writable directory (the default), an unprivileged attacker may predict a privileged process's log file path and pre-create a symbolic link to a sensitive file in its place. When that privileged process runs, it will follow the planted symlink and overwrite that sensitive file. To fix that, glog now causes the program to exit (with status code 2) when it finds that the configured log file already exists.
Publish Date: 2025-01-28
URL: CVE-2024-45339
CVSS 3 Score Details (7.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Release Date: 2025-01-28
Fix Resolution: github.com/golang/glog-v1.2.4
Vulnerable Library - github.com/hashiCorp/go-retryablehttp-v0.7.5
Library home page: https://proxy.golang.org/github.com/hashi!corp/go-retryablehttp/@v/v0.7.5.zip
Path to dependency file: /go.work
Path to vulnerable library: /home/wss-scanner/go/pkg/mod/cache/download/github.com/hashicorp/go-retryablehttp/@v/v0.7.5.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:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.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
Vulnerable Library - github.com/grafana/grafana-plugin-sdk-go-v0.243.0
Library home page: https://proxy.golang.org/github.com/grafana/grafana-plugin-sdk-go/@v/v0.243.0.zip
Path to dependency file: /go.work
Path to vulnerable library: /grafana-plugin-sdk-go/@v/v0.243.0.mod
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
The grafana plugin SDK bundles build metadata into the binaries it compiles; this metadata includes the repository URI for the plugin being built, as retrieved by running
git remote get-url origin.If credentials are included in the repository URI (for instance, to allow for fetching of private dependencies), the final binary will contain the full URI, including said credentials.
Publish Date: 2024-09-19
URL: CVE-2024-8986
CVSS 3 Score Details (5.9)
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: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Release Date: 2024-09-19
Fix Resolution: github.com/grafana/grafana-plugin-sdk-go-v0.250.0
Vulnerable Library - golang.org/x/net-v0.28.0
Library home page: https://proxy.golang.org/golang.org/x/net/@v/v0.28.0.zip
Path to dependency file: /go.work
Path to vulnerable library: /home/wss-scanner/go/pkg/mod/cache/download/golang.org/x/net/@v/v0.28.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:
- 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: Low
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Release Date: 2024-12-18
Fix Resolution: github.com/golang/net-v0.33.0
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.work
Path to vulnerable library: /home/wss-scanner/go/pkg/mod/cache/download/github.com/golang-jwt/jwt/v4/@v/v4.5.0.mod
Dependency Hierarchy:
Found in base branch: main
Vulnerability Details
golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in
ParseWithClaimscan 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 byParseWithClaimsreturn both error codes. If users only check for thejwt.ErrTokenExpiredusingerror.Is, they will ignore the embeddedjwt.ErrTokenSignatureInvalidand thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from thev5branch to thev4branch. In this logic, theParseWithClaimsfunction 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
The text was updated successfully, but these errors were encountered: