{"vuid":"VU#536044","idnumber":"536044","name":"OpenSSL leaks ECDSA private key through a remote timing attack","keywords":["OpenSSL","Side-channel attacks","timing attacks","elliptic curve cryptography","lattice attacks"],"overview":"The OpenSSL ladder implementation for scalar multiplication of points on elliptic curves over binary fields is susceptible to a timing attack vulnerability. This vulnerability can be used to steal the private key of a TLS server that authenticates with ECDSA signatures and binary curves.","clean_desc":"Billy Bob Brumley's and Nicola Tuveri's paper \"Remote Timing Attacks are Still Practical\" states: \"For over two decades, timing attacks have been an active area of research within applied cryptography. These attacks exploit cryptosystem or protocol implementations that do not run in constant time. When implementing an elliptic curve cryptosystem that provides side-channel resistance, the scalar multiplication routine is a critical component. In such instances, one attractive method often suggested in the literature is Montgomery’s ladder that performs a fixed sequence of curve and field operations. This paper describes a timing attack vulnerability in OpenSSL's ladder implementation for curves over binary fields. We use this vulnerability to steal the private key of a TLS server where the server authenticates with ECDSA signatures. Using the timing of the exchanged messages, the messages themselves, and the signatures, we mount a lattice attack that recovers the private key.\"","impact":"A remote attacker can retrieve the private key of a TLS server that authenticates with ECDSA signatures and binary curves.","resolution":"We are currently unaware of a practical solution to this problem.","workarounds":"Do not use ECDSA signatures and binary curves for authentication.","sysaffected":"","thanks":"Thanks to Billy Brumley for reporting this vulnerability.","author":"This document was written by Jared Allar.","public":["http://www.openssl.org/docs/crypto/ecdsa.html","http://eprint.iacr.org/2011/232"],"cveids":["CVE-2011-1945"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2011-03-29T14:10:14Z","publicdate":"2011-05-17T00:00:00Z","datefirstpublished":"2011-05-17T11:43:02Z","dateupdated":"2011-06-01T15:39:27Z","revision":14,"vrda_d1_directreport":"1","vrda_d1_population":"2","vrda_d1_impact":"2","cam_widelyknown":"8","cam_exploitation":"10","cam_internetinfrastructure":"17","cam_population":"1","cam_impact":"17","cam_easeofexploitation":"4","cam_attackeraccessrequired":"3","cam_scorecurrent":"0.133875","cam_scorecurrentwidelyknown":"0.179775","cam_scorecurrentwidelyknownexploited":"0.218025","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":0.133875,"vulnote":null}