… Receiving the bug bounty report The bug bounty report described a way for any user with push access to a repository, including a repository they created themselves, to achieve arbitrary command execution on the GitHub server handling their git push operation. …
… Safeguarding VS Code against prompt injections When a chat conversation is poisoned by indirect prompt injection, it can result in the exposure of GitHub tokens, confidential files, or even the execution of arbitrary code without the user’s explicit consent. …
… These vulnerabilities could have allowed attackers to leak local GitHub tokens, access sensitive files, or even execute arbitrary code without any user confirmation. I’ll also discuss some unique features in VS Code that help mitigate these risks and keep you safe. …
… Safeguarding VS Code against prompt injections When a chat conversation is poisoned by indirect prompt injection, it can result in the exposure of GitHub tokens, confidential files, or even the execution of arbitrary code without the user’s explicit consent. …
… This opened up a path to run arbitrary code and exfiltrate production secrets in these more trusted workflows. …
… These protections hold even if an untrusted user-level component is compromised and executes arbitrary code within its container isolation boundary. …
… Safeguarding VS Code against prompt injections When a chat conversation is poisoned by indirect prompt injection, it can result in the exposure of GitHub tokens, confidential files, or even the execution of arbitrary code without the user’s explicit consent. …
… Remote code execution vulnerabilities in these applications without a sandboxed escape are generally not considered a security risk. Given these caveats, it pays to first go through the source code to get an understanding of the functionalities and intended purpose of code. …
… As a companion to code complexity, the accessibility agent is instructed to avoid attempting code generation for patterns the accessibility team has identified as high-risk. …