The Experts below are selected from a list of 3915 Experts worldwide ranked by ideXlab platform
Vitaly Shmatikov - One of the best experts on this subject based on the ideXlab platform.
-
using frankencerts for automated adversarial testing of Certificate validation in ssl tls implementations
IEEE Symposium on Security and Privacy, 2014Co-Authors: Chad Brubaker, Suman Jana, Sarfraz Khurshid, Vitaly ShmatikovAbstract: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.
Chad Brubaker - One of the best experts on this subject based on the ideXlab platform.
-
using frankencerts for automated adversarial testing of Certificate validation in ssl tls implementations
IEEE Symposium on Security and Privacy, 2014Co-Authors: Chad Brubaker, Suman Jana, Sarfraz Khurshid, Vitaly ShmatikovAbstract: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.
Honig Andrew - One of the best experts on this subject based on the ideXlab platform.
-
A Cpu-Instruction-Based Asymmetric Signing/Decryption Mechanism For Secure Handling Of Asymmetric Keys
Technical Disclosure Commons, 2018Co-Authors: Savagaonkar Uday, Honig AndrewAbstract:A method and system are disclosed for allowing a central processing unit (CPU) to perform signing/decryption operations securely. The system includes the CPU, which embeds an asymmetric private decryption key called CPU Decryption Key (CDK). A public key corresponding to the CDK, known as CPU Encryption Key (CEK) is published by the CPU vendor, and comes with a vendor-Signed Certificate. The CPU exposes two instructions - IMPORT_KEY and USE_KEY, which point to memory locations for storing decrypted keys, wrapped keys, and data. The disclosed mechanism provides a high level of security in cloud environments by providing a secure key delivery to the signer and protecting the signer. In addition, it involves low cost when compared to hardware security modules(HSM)
Suman Jana - One of the best experts on this subject based on the ideXlab platform.
-
using frankencerts for automated adversarial testing of Certificate validation in ssl tls implementations
IEEE Symposium on Security and Privacy, 2014Co-Authors: Chad Brubaker, Suman Jana, Sarfraz Khurshid, Vitaly ShmatikovAbstract: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.
Sarfraz Khurshid - One of the best experts on this subject based on the ideXlab platform.
-
using frankencerts for automated adversarial testing of Certificate validation in ssl tls implementations
IEEE Symposium on Security and Privacy, 2014Co-Authors: Chad Brubaker, Suman Jana, Sarfraz Khurshid, Vitaly ShmatikovAbstract: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.