Skip to content

Update module golang.org/x/crypto to v0.45.0 [SECURITY]#17

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

Update module golang.org/x/crypto to v0.45.0 [SECURITY]#17
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/go-golang.org-x-crypto-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Dec 16, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
golang.org/x/crypto v0.17.0v0.45.0 age adoption passing 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: Never, 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 renovate bot changed the title Update module golang.org/x/crypto to v0.31.0 [SECURITY] Update module golang.org/x/crypto to v0.31.0 [SECURITY] - autoclosed Sep 23, 2025
@renovate renovate bot closed this Sep 23, 2025
@renovate renovate bot deleted the renovate/go-golang.org-x-crypto-vulnerability branch September 23, 2025 14:41
@renovate renovate bot changed the title Update module golang.org/x/crypto to v0.31.0 [SECURITY] - autoclosed Update module golang.org/x/crypto to v0.31.0 [SECURITY] Sep 23, 2025
@renovate renovate bot reopened this Sep 23, 2025
@renovate renovate bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from ea3a4e0 to 8c7c647 Compare September 23, 2025 17:51
@renovate renovate bot changed the title Update module golang.org/x/crypto to v0.31.0 [SECURITY] Update module golang.org/x/crypto to v0.35.0 [SECURITY] Sep 23, 2025
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Sep 23, 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):

  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.20 -> 1.23.0

@bitrise-ip-bot
Copy link
Copy Markdown

bitrise-ip-bot commented Sep 23, 2025

Summary

Security update for golang.org/x/crypto from v0.17.0 to v0.31.0, addressing CVE-2024-45337 (SSH authorization bypass vulnerability) and CVE-2025-22869 (SSH denial of service vulnerability). The update correctly modifies dependency files with proper checksums.

Walkthrough

File Summary
go.mod, go.sum Updated golang.org/x/crypto dependency and checksums

@renovate renovate bot changed the title Update module golang.org/x/crypto to v0.35.0 [SECURITY] Update module golang.org/x/crypto to v0.35.0 [SECURITY] - autoclosed Mar 16, 2026
@renovate renovate bot closed this Mar 16, 2026
@renovate renovate bot changed the title Update module golang.org/x/crypto to v0.35.0 [SECURITY] - autoclosed Update module golang.org/x/crypto to v0.45.0 [SECURITY] Mar 16, 2026
@renovate renovate bot reopened this Mar 16, 2026
@renovate renovate bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch 2 times, most recently from 8c7c647 to 84c0bd4 Compare March 16, 2026 17:37
@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Mar 16, 2026

ℹ️ 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):

  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.20 -> 1.24.0

@renovate renovate bot changed the title Update module golang.org/x/crypto to v0.45.0 [SECURITY] Update module golang.org/x/crypto to v0.45.0 [SECURITY] - autoclosed Mar 27, 2026
@renovate renovate bot closed this Mar 27, 2026
@renovate renovate bot changed the title Update module golang.org/x/crypto to v0.45.0 [SECURITY] - autoclosed Update module golang.org/x/crypto to v0.45.0 [SECURITY] Apr 1, 2026
@renovate renovate bot reopened this Apr 1, 2026
@renovate renovate bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch 2 times, most recently from 84c0bd4 to f375e26 Compare April 1, 2026 19:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant