Update module golang.org/x/crypto from `v0.9.0` to `v0.52.0` [SECURITY] by figure-renovate[bot] · Pull Request #37 · FigureTechnologies/extkey

figure-renovate · 2024-12-03T00:37:14Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
golang.org/x/crypto	`v0.9.0` → `v0.52.0`

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

Prefix Truncation Attack against ChaCha20-Poly1305 and Encrypt-then-MAC aka Terrapin

CVE-2023-48795 / GHSA-45x7-px36-x8w8

More information

Details

Summary

Terrapin is a prefix truncation attack targeting the SSH protocol. More precisely, Terrapin breaks the integrity of SSH's secure channel. By carefully adjusting the sequence numbers during the handshake, an attacker can remove an arbitrary amount of messages sent by the client or server at the beginning of the secure channel without the client or server noticing it.

Mitigations

To mitigate this protocol vulnerability, OpenSSH suggested a so-called "strict kex" which alters the SSH handshake to ensure a Man-in-the-Middle attacker cannot introduce unauthenticated messages as well as convey sequence number manipulation across handshakes.

Warning: To take effect, both the client and server must support this countermeasure.

As a stop-gap measure, peers may also (temporarily) disable the affected algorithms and use unaffected alternatives like AES-GCM instead until patches are available.

Details

The SSH specifications of ChaCha20-Poly1305 (chacha20-poly1305@openssh.com) and Encrypt-then-MAC (*-etm@openssh.com MACs) are vulnerable against an arbitrary prefix truncation attack (a.k.a. Terrapin attack). This allows for an extension negotiation downgrade by stripping the SSH_MSG_EXT_INFO sent after the first message after SSH_MSG_NEWKEYS, downgrading security, and disabling attack countermeasures in some versions of OpenSSH. When targeting Encrypt-then-MAC, this attack requires the use of a CBC cipher to be practically exploitable due to the internal workings of the cipher mode. Additionally, this novel attack technique can be used to exploit previously unexploitable implementation flaws in a Man-in-the-Middle scenario.

The attack works by an attacker injecting an arbitrary number of SSH_MSG_IGNORE messages during the initial key exchange and consequently removing the same number of messages just after the initial key exchange has concluded. This is possible due to missing authentication of the excess SSH_MSG_IGNORE messages and the fact that the implicit sequence numbers used within the SSH protocol are only checked after the initial key exchange.

In the case of ChaCha20-Poly1305, the attack is guaranteed to work on every connection as this cipher does not maintain an internal state other than the message's sequence number. In the case of Encrypt-Then-MAC, practical exploitation requires the use of a CBC cipher; while theoretical integrity is broken for all ciphers when using this mode, message processing will fail at the application layer for CTR and stream ciphers.

For more details see https://terrapin-attack.com.

Impact

This attack targets the specification of ChaCha20-Poly1305 (chacha20-poly1305@openssh.com) and Encrypt-then-MAC (*-etm@openssh.com), which are widely adopted by well-known SSH implementations and can be considered de-facto standard. These algorithms can be practically exploited; however, in the case of Encrypt-Then-MAC, we additionally require the use of a CBC cipher. As a consequence, this attack works against all well-behaving SSH implementations supporting either of those algorithms and can be used to downgrade (but not fully strip) connection security in case SSH extension negotiation (RFC8308) is supported. The attack may also enable attackers to exploit certain implementation flaws in a man-in-the-middle (MitM) scenario.

Severity

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

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

golang.org/x/crypto: Invoking VerifiedPublicKeyCallback permissions skip enforcement

CVE-2026-46595 / GHSA-x527-x647-q7gg

More information

Details

Previously, CVE-2024-45337 fixed an authorization bypass for misused ssh server configurations; if any other type of callback is passed other than public key, then the source-address validation would be skipped.

Severity

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

References

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

golang.org/x/crypto: FIDO/U2F security key physical presence check can be bypassed

CVE-2026-39831 / GHSA-89gr-r52h-f8rx

More information

Details

The Verify() method for FIDO/U2F security key types (sk-ecdsa-sha2-nistp256@openssh.com, sk-ssh-ed25519@openssh.com) did not check the User Presence flag. Signatures generated without physical touch were accepted, allowing unattended use of a hardware security key. To restore the previous behavior, return a "no-touch-required" extension in Permissions.Extensions from PublicKeyCallback.

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 auth bypass via unenforced @revoked status

CVE-2026-42508 / GHSA-5cgq-3rg8-m6cv

More information

Details

Previously, a revoked 'SignatureKey' belonging to a CA was not correctly checked for revocation. Now, both the 'key' and 'key.SignatureKey' are checked for @revoked.

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 doesn't drop invoking agent constraints when forwarding keys

CVE-2026-39832 / GHSA-f5wc-c3c7-36mc

More information

Details

When adding a key to a remote agent constraint extensions such as restrict-destination-v00@openssh.com were not serialized in the request. Destination restrictions were silently stripped when forwarding keys, allowing unrestricted use of the key on the remote host. The client now serializes all constraint extensions. Additionally, the in-memory keyring returned by NewKeyring() now rejects keys with unsupported constraint extensions instead of silently ignoring them.

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 infinite loop on large channel writes

CVE-2026-39834 / GHSA-rm3j-f69w-wqmq

More information

Details

When writing data larger than 4GB in a single Write call on an SSH channel, an integer overflow in the internal payload size calculation caused the write loop to spin indefinitely, sending empty packets without making progress. The size comparison now uses int64 to prevent truncation.

Severity

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

References

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

golang.org/x/crypto: Invoking pathological RSA/DSA parameters may cause DoS

CVE-2026-39829 / GHSA-w879-237q-wc7r

More information

Details

The RSA and DSA public key parsers did not enforce size limits on key parameters. A crafted public key with an excessively large modulus or DSA parameter could cause several minutes of CPU consumption during signature verification. This could be triggered by unauthenticated clients during public key authentication. RSA moduli are now limited to 8192 bits, and DSA parameters are validated per FIPS 186-2.

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 vulnerable to invoking bypass of certificate restrictions

CVE-2026-39828 / GHSA-45gg-vh54-h5m9

More information

Details

When an SSH server authentication callback returned PartialSuccessError with non-nil Permissions, those permissions were silently discarded, potentially dropping certificate restrictions such as force-command after a second factor succeeded. Returning non-nil Permissions with PartialSuccessError now

figure-renovate · 2024-12-03T00:37:15Z

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

4 additional dependencies were updated
The go directive was updated for compatibility reasons

Details:

Package	Change
`go`	`1.18` -> `1.24.0`
`golang.org/x/net`	`v0.10.0` -> `v0.47.0`
`golang.org/x/sys`	`v0.8.0` -> `v0.38.0`
`golang.org/x/term`	`v0.8.0` -> `v0.37.0`
`golang.org/x/text`	`v0.9.0` -> `v0.31.0`

figure-renovate · 2026-03-31T01:40:05Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum

Command failed: go get -t ./...
go: github.com/FigureTechnologies/extkey/cmd/extkey/commands imports
	github.com/btcsuite/btcd/btcec: cannot find module providing package github.com/btcsuite/btcd/btcec
go: github.com/FigureTechnologies/extkey/cmd/extkey/commands imports
	github.com/btcsuite/btcutil/bech32: cannot find module providing package github.com/btcsuite/btcutil/bech32
go: github.com/FigureTechnologies/extkey/cmd/extkey/commands imports
	github.com/gogo/protobuf/proto: cannot find module providing package github.com/gogo/protobuf/proto
go: github.com/FigureTechnologies/extkey/cmd/extkey/commands imports
	github.com/tyler-smith/go-bip32: cannot find module providing package github.com/tyler-smith/go-bip32
go: github.com/FigureTechnologies/extkey/cmd/extkey/commands imports
	github.com/tyler-smith/go-bip39: cannot find module providing package github.com/tyler-smith/go-bip39
go: github.com/FigureTechnologies/extkey/cmd/extkey/commands imports
	gopkg.in/yaml.v3: cannot find module providing package gopkg.in/yaml.v3
go: github.com/FigureTechnologies/extkey/cmd/extkey/commands imports
	github.com/spf13/cobra imports
	github.com/spf13/pflag: cannot find module providing package github.com/spf13/pflag
go: github.com/FigureTechnologies/extkey/cmd/extkey/commands tested by
	github.com/FigureTechnologies/extkey/cmd/extkey/commands.test imports
	github.com/stretchr/testify/assert: cannot find module providing package github.com/stretchr/testify/assert
go: github.com/FigureTechnologies/extkey/cmd/extkey/commands imports
	github.com/gin-gonic/gin imports
	github.com/gin-gonic/gin/binding imports
	github.com/go-playground/validator/v10 imports
	github.com/go-playground/universal-translator: cannot find module providing package github.com/go-playground/universal-translator

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

cursor · 2026-03-31T01:43:48Z

 module github.com/FigureTechnologies/extkey

-go 1.18
+go 1.24.0


Dockerfile uses Go 1.18, incompatible with new requirements

High Severity

The go.mod now specifies go 1.24.0 (required by golang.org/x/crypto v0.45.0), but docker/Dockerfile still uses golang:1.18 as the build image. Since Go 1.21+, the go directive is a strict minimum version requirement, and golang.org/x/crypto v0.45.0 uses language features unavailable in Go 1.18. The Docker build will fail to compile.

figure-renovate Bot requested a review from a team as a code owner December 3, 2024 00:37

figure-renovate Bot added the dependencies label Dec 3, 2024

figure-renovate Bot changed the title ~~fix(deps): update module golang.org/x/crypto from v0.9.0 to v0.17.0 [security]~~ fix(deps): update module golang.org/x/crypto from v0.9.0 to v0.31.0 [security] Dec 12, 2024

figure-renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from ca18e06 to 5c20e20 Compare December 12, 2024 03:06

figure-renovate Bot changed the title ~~fix(deps): update module golang.org/x/crypto from v0.9.0 to v0.31.0 [security]~~ fix(deps): update module golang.org/x/crypto from v0.9.0 to v0.35.0 [security] Apr 14, 2025

figure-renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from 5c20e20 to 33febc2 Compare April 14, 2025 20:47

figure-renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from 33febc2 to c718765 Compare May 8, 2025 21:24

figure-renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from c718765 to 68bbfe3 Compare June 7, 2025 04:36

figure-renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from 68bbfe3 to d45693b Compare July 10, 2025 12:25

figure-renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch 2 times, most recently from fff839e to 5914cfc Compare August 14, 2025 06:42

figure-renovate Bot changed the title ~~fix(deps): update module golang.org/x/crypto from v0.9.0 to v0.35.0 [security]~~ fix(deps): update module golang.org/x/crypto from v0.9.0 to v0.45.0 [security] Nov 20, 2025

figure-renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from 5914cfc to ecf22a5 Compare November 20, 2025 08:58

figure-renovate Bot changed the title ~~fix(deps): update module golang.org/x/crypto from v0.9.0 to v0.45.0 [security]~~ fix(deps): update module golang.org/x/crypto from v0.9.0 to v0.45.0 [security] - autoclosed Mar 28, 2026

figure-renovate Bot closed this Mar 28, 2026

figure-renovate Bot deleted the renovate/go-golang.org-x-crypto-vulnerability branch March 28, 2026 03:48

figure-renovate Bot changed the title ~~fix(deps): update module golang.org/x/crypto from v0.9.0 to v0.45.0 [security] - autoclosed~~ fix(deps): update module golang.org/x/crypto from v0.9.0 to v0.45.0 [security] Mar 31, 2026

figure-renovate Bot reopened this Mar 31, 2026

figure-renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from 8f05596 to ecf22a5 Compare March 31, 2026 01:40

cursor Bot reviewed Mar 31, 2026

View reviewed changes

figure-renovate Bot changed the title ~~fix(deps): update module golang.org/x/crypto from v0.9.0 to v0.45.0 [security]~~ Update module golang.org/x/crypto from v0.9.0 to v0.45.0 [SECURITY] Apr 29, 2026

Update module golang.org/x/crypto from v0.9.0 to v0.52.0 [SECURITY]

9ef37ad

figure-renovate Bot force-pushed the renovate/go-golang.org-x-crypto-vulnerability branch from ecf22a5 to 9ef37ad Compare July 11, 2026 18:00

figure-renovate Bot changed the title ~~Update module golang.org/x/crypto from v0.9.0 to v0.45.0 [SECURITY]~~ Update module golang.org/x/crypto from v0.9.0 to v0.52.0 [SECURITY] Jul 11, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Update module golang.org/x/crypto from `v0.9.0` to `v0.52.0` [SECURITY] - #37

Update module golang.org/x/crypto from `v0.9.0` to `v0.52.0` [SECURITY]#37
figure-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/go-golang.org-x-crypto-vulnerability

figure-renovate Bot commented Dec 3, 2024 •

edited

Loading

Uh oh!

figure-renovate Bot commented Dec 3, 2024 •

edited

Loading

Uh oh!

figure-renovate Bot commented Mar 31, 2026 •

edited

Loading

Uh oh!

cursor Bot left a comment

Uh oh!

cursor Bot Mar 31, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

figure-renovate Bot commented Dec 3, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

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

Details

Severity

References

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

Details

Severity

References

Prefix Truncation Attack against ChaCha20-Poly1305 and Encrypt-then-MAC aka Terrapin

Details

Summary

Mitigations

Details

Impact

Severity

References

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

Details

Severity

References

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

Details

Severity

References

golang.org/x/crypto: Invoking VerifiedPublicKeyCallback permissions skip enforcement

Details

Severity

References

golang.org/x/crypto: FIDO/U2F security key physical presence check can be bypassed

Details

Severity

References

golang.org/x/crypto vulnerable to auth bypass via unenforced @​revoked status

Details

Severity

References

golang.org/x/crypto doesn't drop invoking agent constraints when forwarding keys

Details

Severity

References

golang.org/x/crypto vulnerable to infinite loop on large channel writes

Details

Severity

References

golang.org/x/crypto: Invoking pathological RSA/DSA parameters may cause DoS

Details

Severity

References

golang.org/x/crypto vulnerable to invoking bypass of certificate restrictions

Details

Uh oh!

figure-renovate Bot commented Dec 3, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

ℹ Artifact update notice

File name: go.mod

Uh oh!

figure-renovate Bot commented Mar 31, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ Artifact update problem

File name: go.sum

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

Uh oh!

cursor Bot Mar 31, 2026

Choose a reason for hiding this comment

Dockerfile uses Go 1.18, incompatible with new requirements

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

figure-renovate Bot commented Dec 3, 2024 •

edited

Loading

golang.org/x/crypto vulnerable to auth bypass via unenforced @revoked status

figure-renovate Bot commented Dec 3, 2024 •

edited

Loading

figure-renovate Bot commented Mar 31, 2026 •

edited

Loading