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
Is your feature request related to a problem? Please describe.
The current loki docker image might be affected by an possible misuse of ServerConfig.PublicKeyCallback, which may cause authorization bypass in golang.org/x/crypto. This issue (and it's fix in crypto) is assinged to CVE-2024-45337 / GHSA-v778-237x-gjrc.
Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass. 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.
Describe the solution you'd like
Upgrade golang.org/x/crypto to v0.31.0 - hence merging this PRs would be great:
Is your feature request related to a problem? Please describe.
The current loki docker image might be affected by an possible misuse of ServerConfig.PublicKeyCallback, which may cause authorization bypass in
golang.org/x/crypto
. This issue (and it's fix in crypto) is assinged to CVE-2024-45337 / GHSA-v778-237x-gjrc.Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass. 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.
Describe the solution you'd like
Upgrade
golang.org/x/crypto
tov0.31.0
- hence merging this PRs would be great:Additional context - Details from Image-Scan
The text was updated successfully, but these errors were encountered: