OpenSSH 10.3 Fixes Five Critical Vulnerabilities and Removes Legacy Rekeying Support, Disrupting Incompatible SSH Deployments
What Happened — OpenSSH 10.3 was released, addressing five security bugs: a shell‑injection flaw via user‑name tokens, a certificate‑principal matching error, improper ECDSA algorithm enforcement, and two behavior changes that tighten certificate handling. The update also drops legacy rekeying support, causing older SSH clients/servers that lack rekeying to fail interoperability.
Why It Matters for TPRM —
- SSH is a foundational protocol for remote administration, CI/CD pipelines, and data‑center connectivity; unpatched implementations expose third‑party environments to command‑execution attacks.
- The removal of legacy rekeying can break integrations with legacy vendors, creating service‑availability risks for supply‑chain partners.
- Many regulated industries (finance, healthcare, cloud SaaS) rely on OpenSSH‑based appliances; a vulnerability in a vendor’s stack propagates to your risk posture.
Who Is Affected — Cloud‑infrastructure providers, SaaS platforms, managed service providers, financial services, healthcare IT, and any organization that runs SSH servers or clients on Linux/Unix systems.
Recommended Actions —
- Inventory all assets running OpenSSH ≤ 10.2 and verify upgrade paths to 10.3 or later.
- Test compatibility with legacy SSH endpoints before applying the patch; consider maintaining a separate bastion for legacy systems.
- Require vendors to provide proof of patch deployment and rekeying‑support verification.
- Update hardening guides to disallow user‑supplied usernames containing shell metacharacters.
Technical Notes — The shell‑injection issue stems from a timing flaw in %u token expansion within ssh_config. The certificate‑principal bug mis‑matches principals containing commas, potentially granting unintended access. ECDSA enforcement previously allowed any ECDSA algorithm if one was listed, now correctly restricts to the explicit set. Legacy rekeying code was removed, breaking interoperability with SSH implementations that never implemented the rekeying extension. Source: Help Net Security