Skip to content

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

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]#202
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 12, 2024

This PR contains the following updates:

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

Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto

CVE-2024-45337 / GHSA-v778-237x-gjrc

More information

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

Severity

  • CVSS Score: 9.1 / 10 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


golang.org/x/crypto Vulnerable to Denial of Service (DoS) via Slow or Incomplete Key Exchange

CVE-2025-22869 / GHSA-hcg3-q754-cr77

More information

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.

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


golang.org/x/crypto/ssh allows an attacker to cause unbounded memory consumption

CVE-2025-58181 / GHSA-j5w8-q4qc-rx2x

More information

Details

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.

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


golang.org/x/crypto/ssh/agent vulnerable to panic if message is malformed due to out of bounds read

CVE-2025-47914 / GHSA-f6x5-jh6r-wrfv

More information

Details

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.

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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 renovate Bot added the renovate label Dec 12, 2024
@renovate
Copy link
Copy Markdown
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):

  • 1 additional dependency was updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.21 -> 1.24.0
golang.org/x/sys v0.23.0 -> v0.38.0

@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] Apr 14, 2025
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from 9104fb0 to c85ef6c Compare April 14, 2025 22:32
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch 2 times, most recently from 241217a to 4ddf3c4 Compare May 9, 2025 16:00
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from 4ddf3c4 to c362815 Compare August 10, 2025 14:00
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from c362815 to f56fabb Compare October 9, 2025 09:46
@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 Oct 23, 2025
@renovate renovate Bot closed this Oct 23, 2025
@renovate renovate Bot deleted the renovate/go-golang.org-x-crypto-vulnerability branch October 23, 2025 10:05
@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.35.0 [SECURITY] Oct 23, 2025
@renovate renovate Bot reopened this Oct 23, 2025
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch 2 times, most recently from f56fabb to 84e07b7 Compare October 23, 2025 14:48
@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.45.0 [SECURITY] Nov 20, 2025
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from 84e07b7 to 3a6e06a Compare November 20, 2025 01:23
@renovate
Copy link
Copy Markdown
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):

  • 1 additional dependency was updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.21 -> 1.24.0
golang.org/x/sys v0.23.0 -> v0.38.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] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch 2 times, most recently from 3a6e06a to 664e8d8 Compare March 30, 2026 22:10
@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 Apr 27, 2026
@renovate renovate Bot closed this Apr 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 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch 2 times, most recently from 664e8d8 to 53ce593 Compare April 27, 2026 23:13
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.

0 participants