Using Frankencerts for Automated Adversarial Testing of Certificate Validation in SSL/TLS Implementations
Top Cited Papers
- 1 May 2014
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- Vol. 2014 (10816011) , 114-129
- https://doi.org/10.1109/sp.2014.15
Abstract
Modern network security rests on the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols. Distributed systems, mobile and desktop applications, embedded devices, and all of secure Web rely on SSL/TLS for protection against network attacks. This protection critically depends on whether SSL/TLS clients correctly validate X.509 certificates presented by servers during the SSL/TLS handshake protocol. We design, implement, and apply the first methodology for large-scale testing of certificate validation logic in SSL/TLS implementations. Our first ingredient is "frankencerts," synthetic certificates that are randomly mutated from parts of real certificates and thus include unusual combinations of extensions and constraints. Our second ingredient is differential testing: if one SSL/TLS implementation accepts a certificate while another rejects the same certificate, we use the discrepancy as an oracle for finding flaws in individual implementations. Differential testing with frankencerts uncovered 208 discrepancies between popular SSL/TLS implementations such as OpenSSL, NSS, CyaSSL, GnuTLS, PolarSSL, MatrixSSL, etc. Many of them are caused by serious security vulnerabilities. For example, any server with a valid X.509 version1 certificate can act as a rogue certificate authority and issue fake certificates for any domain, enabling man-in-the-middle attacks against MatrixSSL and GnuTLS. Several implementations also accept certificate authorities created by unauthorized issuers, as well as certificates not intended for server authentication. We also found serious vulnerabilities in how users are warned about certificate validation errors. When presented with an expired, self-signed certificate, NSS, Safari, and Chrome (on Linux) report that the certificate has expired - a low-risk, often ignored error - but not that the connection is insecure against a man-in-the-middle attack. These results demonstrate that automated adversarial testing with frankencerts is a powerful methodology for discovering security flaws in SSL/TLS implementations.Keywords
This publication has 28 references indexed in Scilit:
- Analysis of the HTTPS certificate ecosystemPublished by Association for Computing Machinery (ACM) ,2013
- Lucky Thirteen: Breaking the TLS and DTLS Record ProtocolsPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2013
- Why eve and mallory love androidPublished by Association for Computing Machinery (ACM) ,2012
- Abusing File Processing in Malware Detectors for Fun and ProfitPublished by Institute of Electrical and Electronics Engineers (IEEE) ,2012
- Finding and understanding bugs in C compilersPublished by Association for Computing Machinery (ACM) ,2011
- Precise interface identification to improve testing and analysis of web applicationsPublished by Association for Computing Machinery (ACM) ,2009
- Automating Software Testing Using Program AnalysisIEEE Software, 2008
- Grammar-based whitebox fuzzingPublished by Association for Computing Machinery (ACM) ,2008
- Debugging in ParallelPublished by Association for Computing Machinery (ACM) ,2007
- DARTPublished by Association for Computing Machinery (ACM) ,2005