About this paper
Mutual TLS in Practice: A Deep Dive into Certificate Configurations and Privacy Issues
Hongying Dong, Yizhe Zhang, Hyeonmin Lee, Kevin Du, Guancheng Tu, and Yixin Sun University of Virginia
This paper has been published at IMC 2024.
Summary
In this research, we investigated the prevalence and characteristics of mutual TLS connections, including the associated services and patterns of certificate usage. Specifically, by analyzing TLS connection logs collected from a large campus network over 23 months, we identified over 2.2 million unique server certificates and over 3.4 million unique client certificates used in over 1.2 billion mutual TLS connections. Using this data, we examined security concerns, non-standard behaviors in certificate sharing, and the privacy implications of sensitive information found in mutual TLS certificates.
Key findings
-
Prevalance of Mutual TLS: 38.45% of the certificates presented by servers and 94.34% of those employed by clients are used in mutual TLS connections. A nearly twofold increase in the overall adoption of mutual TLS authentication is observed, rising from 1.99% to 3.61% of total TLS connections between May 2022 and March 2024. Additionally, while HTTPS is the primary protocol for both mutual and non-mutual TLS connections, mutual TLS has a lower proportion of HTTPS traffic, with various services (e.g., file transfer) using mutual TLS.
-
Concerning practices in certificate usage:
- The absence of a valid client issuer in 37.84% of all observed connections.
- The use of certificates with dummy serial numbers resulting in almost 40,000 collisions within the same issuer.
- Both endpoints employ identical certificates in single connections that involve over 5,000 clients.
- The continued use of client certificates that have been expired for over 1,000 days, with 42.27% issued by and used for Apple and Microsoft services
- Information revealed in CN/ SAN: A diverse range of information is uncovered in the Common Name (CN) and Subject Alternative Name (SAN) fields, many of which include sensitive data. Notably, more than 60,000 client certificates contain personal names or user accounts, raising privacy concerns.