FIDO confirmation ambiguity via silent None authentication
Published Mar 12, 2022 · Updated May 29, 2026
Authentication ambiguity in the OpenSSH client before 8.9 allows remote attackers to obscure what a FIDO confirmation authorizes. The client presents the same FIDO confirmation when authenticating to a modified server that accepts None authentication and when its forwarded agent signs a connection from that server to another host. Reachability requires public-key authentication, agent forwarding, a FIDO key, and non-verbose logging; OpenSSH disputes that this behavior constitutes an authentication bypass.
Summary
What happened
Authentication ambiguity in the OpenSSH client before 8.9 allows remote attackers to obscure what a FIDO confirmation authorizes. The client presents the same FIDO confirmation when authenticating to a modified server that accepts None authentication and when its forwarded agent signs a connection from that server to another host. Reachability requires public-key authentication, agent forwarding, a FIDO key, and non-verbose logging; OpenSSH disputes that this behavior constitutes an authentication bypass.
The record
- CVE
- CVE-2021-36368
- Published
- Mar 12, 2022
- Updated
- May 29, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-287
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2022CVE publishedPublication date reported by the CVE source.
- May 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo