Invoking agent constraints dropped when forwarding keys in golang.org/x/crypto/ssh/agent
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 0.52.0 and golang.org/x/crypto 0.52.0.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| golang.org/x/crypto | <0.52.0 | 0.52.0 | |
| go: golang.org/x/crypto | <0.52.0 | 0.52.0 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in golang.org/x/crypto (Go), strongest first
Embed
A live severity badge for an advisory, README or ticket