TL;DR
This paper introduces Horcrux, a novel password manager designed for "paranoid" users by minimizing trust in both client and server components. It achieves this through a split architecture, secret sharing across multiple servers, and a unique credential swapping mechanism that prevents credentials from ever being exposed to the browser's DOM, demonstrating compatibility with over 98% of tested websites.
What Problem Does This Paper Address?
Password managers are widely recommended for improving online security, but current implementations are plagued by vulnerabilities. These vulnerabilities exist on both the client-side (e.g., malicious scripts stealing credentials from the browser's DOM) and server-side (e.g., database breaches leading to credential theft). Existing solutions often require users to trust a centralized provider or a complex client-side application, creating significant attack surfaces. The paper aims to address the need for a password manager that drastically reduces these attack surfaces and minimizes the trust placed in any single entity, even for highly security-conscious users.
Methods
Horcrux employs a multi-pronged approach to enhance security:
- Client-Side Privilege Separation: The client is divided into a small, auditable "trusted core" that handles sensitive operations (master password access, key derivation) and an "untrusted UI component" that manages the user interface. These components communicate solely through message passing, limiting the attack surface of the trusted code.
- Secret Sharing for Server-Side Storage: Instead of storing credentials on a single server, Horcrux uses secret sharing to distribute them across multiple independent servers. This ensures that compromising a single server does not reveal any user credentials.
- Cuckoo Hashing for Privacy: To prevent offline guessing attacks on the master password, Horcrux uses a variant of cuckoo hashing. This technique stores credentials in a way that makes it impossible for an attacker to determine if a guessed master password is correct without interacting with the actual keystore servers. This also provides domain and username privacy.
- Credential Swapping: When a login form is detected, the untrusted UI component autofills dummy credentials. The trusted core then intercepts outgoing network traffic, swaps the dummy credentials for the real ones just before encryption, and sends them to the server. This prevents credentials from ever being exposed to the browser's DOM or potentially malicious JavaScript.
Datasets
The paper describes a large-scale experiment where they scanned Alexa's top million websites to test the compatibility of their credential swapping technique. This is a newly generated benchmark for evaluating password manager compatibility.
Key Insights and Ideas
- The "Paranoid" User is a Valid Target: The paper acknowledges that users with extreme security concerns require specialized solutions, and Horcrux is designed to meet those needs by minimizing trust.
- Splitting Trust is Key: By separating the client into trusted and untrusted components and distributing server-side trust via secret sharing, Horcrux significantly reduces the impact of individual component compromises.
- DOM Exposure is the Achilles' Heel: The core insight driving the credential swapping mechanism is that preventing credentials from ever touching the DOM is crucial for mitigating common client-side attacks.
- Cuckoo Hashing for Privacy, Not Just Performance: While cuckoo hashing is known for its efficiency, Horcrux creatively adapts it to provide privacy by making credential locations indistinguishable to an attacker.
- Compatibility is Achievable: The 98% compatibility rate with real-world websites demonstrates that these advanced security measures can be implemented without sacrificing broad usability.
Key Results
- High Compatibility: Horcrux's credential swapping technique was found to be compatible with over 98% of tested login forms across Alexa's top million websites.
- Minimal Trusted Code: The trusted component of the Horcrux client consists of approximately 800 lines of JavaScript, making it highly auditable.
- Latency: Microbenchmark tests showed that read and write requests to keystores varied based on geographical distance, with global distribution leading to approximately 1.6 seconds for credential retrieval and 2.5 seconds for account enrollment. These times are noted as potentially noticeable to users.
- Security Against Attacks: The design aims to resist client-side script injection and server-side data breaches, making offline guessing attacks on the master password infeasible.
Limitations and Future Work
- Firefox Add-on Limitations: The prototype is a Firefox add-on, which has limitations in accessing low-level browser APIs needed for full control over HTTPS traffic manipulation. Future work suggests direct browser integration for better security and performance.
- Multiple Accounts per Domain: The current prototype does not support multiple usernames for a single domain. The authors suggest modifications to handle this, potentially involving user interaction to select the correct username.
- User Experience and Latency: While compatible, the latency for credential retrieval and enrollment might be noticeable to users. Future work could focus on optimizing performance, especially with browser integration.
- Cross-Extension Attacks: The add-on model is susceptible to cross-extension attacks, though the authors mitigate this by avoiding global variables. Browser integration would further enhance security.
- Social Engineering: The system does not protect against social engineering attacks where users are tricked into revealing their master password.
- Password Generation: The paper acknowledges that password generation rules are orthogonal to their core research and does not deeply address the complexities of generating passwords that satisfy all website requirements.
Summary updated