Join our Newsletter — 33% off our NHI Course

Why does a compromised host break FIDO2 Client PIN trust?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20217
Topic starter  

TL;DR: A compromised host can undermine FIDO2 Client PIN flow by intercepting PIN entry, relaying requests, and steering approvals, according to Crayonic. Authentication now depends on the workstation’s honesty, so PIN handling and approval display become part of the attack surface.

Editorial analysis by NHI Mgmt Group, based on content published by Crayonic: “Your security key trusts the computer it’s plugged into. That’s the problem.”.

Key questions

Q: Why do compromised endpoints weaken FIDO2-style sign-in even when private keys stay in hardware?

A: Because the attacker does not need the private key to win.

Q: What signs show that an authenticator binding process may be vulnerable to relayed registration?

A: Watch for registrations that originate from high-risk endpoints, unexpected device replacement, and inconsistent device provenance after enrollment.

Q: How should teams reduce risk when a security key still relies on a workstation for PIN entry?

A: Reduce reliance on host-mediated PIN entry by moving verification and approval onto the authenticator wherever possible.

Practitioner guidance

  • Map the workstation to the trust boundary Document where the host participates in PIN entry, approval display, and device binding so you can see which parts of the flow remain exposed if the endpoint is compromised.
  • Prefer local verification on the authenticator Where the environment is shared or high risk, choose devices that verify the user on the token itself rather than routing a PIN through the computer.
  • Require visible transaction context on hardware Use authenticators with an onboard display or equivalent trusted output so the user can confirm the actual request outside the control of the workstation.

Bottom line: The article's central warning is that FIDO2 can remain vulnerable when the computer mediating the session is not trustworthy.

Glossary terms: Account PIN, Authenticator Binding, Parallel session attack, Host-trust minimisation

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20707
 

Host trust is the real weak point in Client PIN flows: the protocol assumes the workstation can safely collect secrets and present approval context, but that assumption fails as soon as the host is compromised. The cryptography can remain intact while the approval path is redirected. For identity programmes, the lesson is that phishing resistance is not the same as host trust elimination.

A few things that frame the scale:

  • 92% of organisations expose NHIs to third parties, raising concerns about supply chain security, according to the Ultimate Guide to NHIs.

A question worth separating out:

Q: What is the difference between phishing-resistant MFA and removing host trust from authentication?

A: Phishing-resistant MFA can stop credential replay and website spoofing, but it still may depend on a workstation to handle input and approval. Removing host trust goes further by moving verification and confirmation to the authenticator itself. The first resists phishing; the second reduces what a compromised endpoint can manipulate during the sign-in flow.

👉 Read our full editorial: FIDO2 client PIN trust breaks when the host is compromised


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.