arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 1709.01552cs.CR
收藏

我们是否从LLC侧信道攻击中学到了什么?一种面向密码库的Cache泄漏检测工具

Did we learn from LLC Side Channel Attacks? A Cache Leakage Detection Tool for Crypto Libraries

Gorka Irazoqui, Kai Cong, Xiaofei Guo, Hareesh Khattri, Arun Kanuparthi, Thomas Eisenbarth, Berk Sunar

摘要:

这项工作提出了一个新的工具来验证密码实现的正确性,相对于缓存攻击。我们的方法发现了其他技术难以发现的漏洞,被视为可利用的泄漏。该方法的工作原理是通过识别秘密相关内存,并在潜在易受攻击的代码中引入强制驱逐,以获得使用互信息分析的缓存跟踪。如果观察到依赖性,则加密实现被分类为泄漏信息。我们证明了我们的技术在三个主要的密码原语的设计,即,AES,RSA和ECC,在八个流行的最新加密库中,包括OpenSSL,Libgcrypt,Intel IPP和NSS。我们的研究结果表明,加密代码设计者远未采用适当的对策来避免缓存泄漏,因为我们发现50%的默认实现分析了导致密钥提取的泄漏信息。我们负责任地通知设计人员发现的所有漏洞,并建议修补程序来解决这些漏洞。

英文摘要:

This work presents a new tool to verify the correctness of cryptographic implementations with respect to cache attacks. Our methodology discovers vulnerabilities that are hard to find with other techniques, observed as exploitable leakage. The methodology works by identifying secret dependent memory and introducing forced evictions inside potentially vulnerable code to obtain cache traces that are analyzed using Mutual Information. If dependence is observed, the cryptographic implementation is classified as to leak information. We demonstrate the viability of our technique in the design of the three main cryptographic primitives, i.e., AES, RSA and ECC, in eight popular up to date cryptographic libraries, including OpenSSL, Libgcrypt, Intel IPP and NSS. Our results show that cryptographic code designers are far away from incorporating the appropriate countermeasures to avoid cache leakages, as we found that 50% of the default implementations analyzed leaked information that lead to key extraction. We responsibly notified the designers of all the leakages found and suggested patches to solve these vulnerabilities.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑