TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

How Malicious extensions hide running arbitrary code

75 pointsby supermatoualmost 2 years ago

2 comments

akkartikalmost 2 years ago
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-landalmost 2 years ago
This is fascinating. Especially that they&#x27;re essentially using a little diy lisp to get around content security policy.