TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

How Malicious extensions hide running arbitrary code

75 点作者 supermatou将近 2 年前

2 条评论

akkartik将近 2 年前
I have so many questions after reading this. Like this example:<p><pre><code> [ &#x2F;&#x2F; Call console.log &quot;@&quot;, [&quot;.&quot;, [&quot;console&quot;], &quot;log&quot;], &#x2F;&#x2F; Verbatim call parameter &quot;hi&quot; ] </code></pre> What sort of sandboxing model is susceptible to this?<p>I can&#x27;t imagine any sort of principled sandboxing model that would be susceptible to running a whole interpreter within. Protections should go on the equivalent of syscalls, the side-effects code can have. We&#x27;ve known this for -- conservatively -- 30 years. Can somebody with knowledge explain how these extensions are breaking Chrome&#x27;s security sandbox?
评论 #36189464 未加载
评论 #36188508 未加载
noman-land将近 2 年前
This is fascinating. Especially that they&#x27;re essentially using a little diy lisp to get around content security policy.