New Passkey Attacks Expose Private Keys and Bypass Phishing-Resistant MFA Without Breaking Encryption

Palo Alto Networks' Unit 42 found three Pass-ta-key attacks targeting Google's passkey implementation. The techniques can expose synced private keys and bypass phishing-resistant multi-factor authentication without breaking FIDO2 encryption.

A USB FIDO security key used for hardware-backed authentication.
Feature image: Bautsch / CC0 / Wikimedia Commons.

Researchers at Palo Alto Networks' Unit 42 have discovered three new attack methods called "Pass-ta-key" that can compromise passkey security. These attacks specifically target Google's passkey implementation and can bypass phishing-resistant Multi-Factor Authentication (MFA) without breaking FIDO2 encryption.

Key Findings

Attack Vectors

  1. Chrome Passkey Sync Vulnerability: Attacks exploit Google Password Manager's synced-passkey system in Chrome on Windows, allowing attackers to recover synced private keys.
  2. Windows Credential UI Manipulation: Uses window-handle spoofing and API manipulation to bypass user verification requirements.
  3. System Logs Exploitation: Leverages Windows logs for authentication bypass.

Attack Methodology

  • All attacks require malware already running on the victim's endpoint (no initial phishing required)
  • Attackers can authenticate without user interaction
  • Private keys are extracted from synced passkey storage
  • Bypasses user verification requirements in Google's implementation

Technical Details

What Makes These Attacks Unique

  • No Encryption Breaking: Unlike traditional attacks, these don't break FIDO2 encryption protocols
  • Bypass Phishing-Resistant MFA: Successfully bypasses MFA mechanisms that are designed to be phishing-resistant
  • Targeted at Google Ecosystem: Specifically affects Google Password Manager and Chrome implementation
  • Uses Existing Infrastructure: Leverages existing Windows and Chrome infrastructure rather than creating new attack vectors

Vulnerability Scope

  • Affected Platforms: Google Chrome on Windows with synced passkeys enabled
  • Affected Storage: Google Password Manager's synced passkey storage
  • Private Keys at Risk: All private keys synced through Google's system share a master key that can be stolen

Impact Assessment

Security Implications

  1. Compromised Authentication: Attackers can authenticate as users without their knowledge or consent
  2. Private Key Exposure: Private keys are exposed, potentially allowing long-term unauthorized access
  3. Bypass of MFA: Bypasses the very security mechanism designed to prevent phishing attacks
  4. Ecosystem Risk: Affects Google's entire passkey ecosystem through shared master key vulnerability

Attack Requirements

  • Initial Compromise: Malware already present on victim's endpoint (typically via phishing or other infection methods)
  • No User Interaction Required: Once malware is installed, authentication can occur silently
  • Targeted Implementation: Specific to Google's passkey implementation, not general FIDO2 standards

Recommendations

For Users

  1. Avoid using synced passkeys in Google Password Manager if possible
  2. Keep systems updated with latest security patches
  3. Implement comprehensive endpoint protection solutions
  4. Monitor for suspicious activity on accounts

For Organizations

  1. Review passkey implementation policies, especially those using Google's ecosystem
  2. Consider alternative passkey implementations that don't rely on shared master keys
  3. Implement additional monitoring for authentication anomalies
  4. Educate users about the risks of malware infections

Conclusion

The Pass-ta-key attacks represent a significant evolution in passkey security threats. While FIDO2 standards remain secure, specific implementations by Google have vulnerabilities that can be exploited by sophisticated attackers. This research highlights the importance of not just implementing security protocols correctly, but also ensuring proper ecosystem security when using third-party services.

This finding is particularly concerning because it shows that even phishing-resistant authentication mechanisms can be bypassed through implementation flaws in specific software ecosystems.

Feature image: Bautsch / CC0 / Wikimedia Commons.