Critical · published March 17, 2023
⚠️ A sneaky oversight in OpenSSH could let smartcard keys be added without the right restrictions – like a bouncer letting in guests who aren’t on the list! Think of an event where the security staff are supposed to check IDs at the door. If they let anyone in without verifying their credentials, it could lead to unauthorized access, and chaos could ensue! Without the intended destination constraints, an unauthorized user could potentially manipulate this flaw to add their own keys, gaining access to systems that should be secured. Imagine an uninvited party crasher who not only enters the event but also takes control of the entire dance floor!
Think of an event where the security staff are supposed to check IDs at the door. If they let anyone in without verifying their credentials, it could lead to unauthorized access, and chaos could ensue! In OpenSSH versions prior to 9.3, the `ssh-add` command incorrectly allows smartcard keys to be added to the ssh-agent without enforcing the necessary per-hop destination constraints, leading to potential unauthorized access.
Without the intended destination constraints, an unauthorized user could potentially manipulate this flaw to add their own keys, gaining access to systems that should be secured. Imagine an uninvited party crasher who not only enters the event but also takes control of the entire dance floor! To mitigate this, update to OpenSSH version 9.3 or later as soon as possible. Regularly audit your key management practices and ensure that proper access controls are in place to prevent unauthorized additions to the ssh-agent. You’ve got this! Stay vigilant and keep your systems secure! 🛡️
| Product | Versions | Fixed in |
|---|---|---|
| openbsd/openssh | ≥ 8.9, < 9.3 | 9.3 |
| netapp/brocade_fabric_operating_system | all versions | — |
| netapp/hci_bootstrap_os | all versions | — |
| netapp/solidfire_element_os | all versions | — |