Skip to content

fix(deps): update module golang.org/x/crypto to v0.45.0 [security]#103

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/go-golang.org-x-crypto-vulnerability
Open

fix(deps): update module golang.org/x/crypto to v0.45.0 [security]#103
renovate[bot] wants to merge 1 commit intomainfrom
renovate/go-golang.org-x-crypto-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 12, 2024

This PR contains the following updates:

Package Change Age Confidence
golang.org/x/crypto v0.24.0v0.45.0 age confidence

GitHub Vulnerability Alerts

CVE-2024-45337

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/crypto@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.

CVE-2025-22869

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.

CVE-2025-58181

SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in the request, allowing an attacker to cause unbounded memory consumption.

CVE-2025-47914

SSH Agent servers do not validate the size of messages when processing new identity requests, which may cause the program to panic if the message is malformed due to an out of bounds read.


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Dec 12, 2024

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 7 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.21 -> 1.24.0
golang.org/x/mod v0.17.0 -> v0.29.0
golang.org/x/net v0.25.0 -> v0.47.0
golang.org/x/sync v0.7.0 -> v0.18.0
golang.org/x/sys v0.21.0 -> v0.38.0
golang.org/x/term v0.21.0 -> v0.37.0
golang.org/x/text v0.16.0 -> v0.31.0
golang.org/x/tools v0.21.1-0.20240508182429-e35e4ccd0d2d -> v0.38.0

@renovate renovate bot requested a review from a team as a code owner December 12, 2024 00:30
@renovate renovate bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from 8481ac0 to db4875b Compare March 6, 2025 08:55
@renovate renovate bot changed the title fix(deps): update module golang.org/x/crypto to v0.31.0 [security] fix(deps): update module golang.org/x/crypto to v0.35.0 [security] Apr 14, 2025
@renovate renovate bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from db4875b to 90ecea1 Compare April 14, 2025 21:39
@renovate renovate bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from 90ecea1 to 1423bc8 Compare May 7, 2025 10:06
@renovate renovate bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch 3 times, most recently from f7c21cd to 87e50ec Compare May 22, 2025 07:03
@renovate renovate bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from 87e50ec to 7c8c7aa Compare July 23, 2025 13:15
@renovate renovate bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from 7c8c7aa to 8fc1ee7 Compare August 10, 2025 15:48
@renovate renovate bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from 8fc1ee7 to de15522 Compare October 9, 2025 12:05
@renovate renovate bot changed the title fix(deps): update module golang.org/x/crypto to v0.35.0 [security] fix(deps): update module golang.org/x/crypto to v0.45.0 [security] Nov 20, 2025
@renovate renovate bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from de15522 to 74e96a1 Compare November 20, 2025 02:32
@renovate
Copy link
Contributor Author

renovate bot commented Dec 15, 2025

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 7 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.21 -> 1.24.0
golang.org/x/mod v0.17.0 -> v0.29.0
golang.org/x/net v0.25.0 -> v0.47.0
golang.org/x/sync v0.7.0 -> v0.18.0
golang.org/x/sys v0.21.0 -> v0.38.0
golang.org/x/term v0.21.0 -> v0.37.0
golang.org/x/text v0.16.0 -> v0.31.0
golang.org/x/tools v0.21.1-0.20240508182429-e35e4ccd0d2d -> v0.38.0

@renovate renovate bot changed the title fix(deps): update module golang.org/x/crypto to v0.45.0 [security] fix(deps): update module golang.org/x/crypto to v0.45.0 [security] - autoclosed Jan 14, 2026
@renovate renovate bot closed this Jan 14, 2026
@renovate renovate bot deleted the renovate/go-golang.org-x-crypto-vulnerability branch January 14, 2026 03:18
@renovate renovate bot changed the title fix(deps): update module golang.org/x/crypto to v0.45.0 [security] - autoclosed fix(deps): update module golang.org/x/crypto to v0.45.0 [security] Jan 14, 2026
@renovate renovate bot reopened this Jan 14, 2026
@renovate renovate bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch 2 times, most recently from 74e96a1 to 7c4025c Compare January 14, 2026 07:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants