CVE-2023-28531: ssh-add in OpenSSH before 9.3 adds smartcard keys to ssh-agent without the intended per-hop destination con...
ssh-add in OpenSSH before 9.3 adds smartcard keys to ssh-agent without the intended per-hop destination constraints. The earliest affected version is 8.9.
Security readout for executives and security teams
Plain-English summary
OpenSSH ssh-add could add smartcard-backed keys to ssh-agent without the intended per-hop destination limits. If an organization relies on those limits to control where a smartcard key may be used, affected clients may weaken that control. The bundle does not provide CVSS, confirmed exploitation, or product-specific impact beyond referenced advisories.
Executive priority
Treat as a targeted access-control issue, not a broad remote-code-execution emergency. Prioritize privileged users, administrators, CI operators, and environments relying on smartcard SSH keys with agent forwarding controls.
Technical view
CVE-2023-28531 affects OpenSSH ssh-add from 8.9 through versions before 9.3. The issue is an access-control weakness where smartcard keys added to ssh-agent may miss destination constraints. The CVE maps to CWE-284. KEV is false, and the provided sources do not include exploit details or a CVSS score.
Likely exposure
Likely exposure is systems running OpenSSH 8.9 to before 9.3 where users add smartcard keys to ssh-agent with destination constraints. Appliances or packaged distributions referenced by NetApp, Gentoo, Debian, Fedora, and Siemens should be checked against vendor guidance.
Exploitation context
The provided bundle does not show active exploitation, CISA KEV listing, public exploit code, or weaponized use. Risk depends on whether smartcard keys and agent destination constraints are used in real workflows.
Researcher notes
Evidence is narrow but consistent: ssh-add mishandles destination constraints for smartcard keys in OpenSSH before 9.3, earliest affected 8.9. The bundle lacks CVSS, exploit telemetry, and full downstream affected-version matrices, so product-specific conclusions require vendor advisory review.
Mitigation direction
Upgrade OpenSSH to 9.3 or a vendor-patched package.
Apply relevant Gentoo, Debian, Fedora, NetApp, or Siemens guidance where applicable.
Inventory workflows using ssh-add smartcard keys and destination constraints.
Do not rely solely on destination constraints until affected clients are patched.
Validation and detection
Identify OpenSSH client versions on administrator and developer workstations.
Confirm whether smartcard-backed keys are added to ssh-agent.
Review whether destination constraints are used in SSH agent workflows.
Check vendor advisories for distribution or appliance-specific fixed versions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.