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

投机型混淆漏洞的分析

An Analysis of Speculative Type Confusion Vulnerabilities in the Wild

Ofek Kirzner, Adam Morrison

摘要:

Spectre v1攻击利用条件分支误预测,通常被识别为绕过数组边界检查以从受害者的内存中泄漏数据的攻击。然而,一般来说,Spectre v1攻击可以利用任何条件分支错误预测,使受害者错误地执行代码。在本文中,我们调查投机类型混淆,一个幽灵v1攻击向量,其中分支预测失误,使受害者执行的变量持有错误类型的值,从而泄漏内存内容。我们观察到编译器可能无意中引入推测类型混淆,使程序员很难推理安全性并手动应用Spectre缓解措施。因此,我们开始确定推测类型混淆影响Linux内核的程度。我们的分析发现了可利用和潜在可利用的任意内存泄漏漏洞。我们还发现了许多潜在的漏洞,这些漏洞可能由于无害的系统更改(如编码风格更改)而被利用。我们的研究结果表明,依赖于静态/手动识别“坏”代码模式的Spectre缓解措施需要重新考虑,并且需要更全面的缓解措施。

英文摘要:

Spectre v1 attacks, which exploit conditional branch misprediction, are often identified with attacks that bypass array bounds checking to leak data from a victim's memory. Generally, however, Spectre v1 attacks can exploit any conditional branch misprediction that makes the victim execute code incorrectly. In this paper, we investigate speculative type confusion, a Spectre v1 attack vector in which branch mispredictions make the victim execute with variables holding values of the wrong type and thereby leak memory content. We observe that speculative type confusion can be inadvertently introduced by a compiler, making it extremely hard for programmers to reason about security and manually apply Spectre mitigations. We thus set out to determine the extent to which speculative type confusion affects the Linux kernel. Our analysis finds exploitable and potentially-exploitable arbitrary memory disclosure vulnerabilities. We also find many latent vulnerabilities, which could become exploitable due to innocuous system changes, such as coding style changes. Our results suggest that Spectre mitigations which rely on statically/manually identifying "bad" code patterns need to be rethought, and more comprehensive mitigations are needed.

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

↑