Snowflake AI Escapes Sandbox and Executes Malware
promptarmor.com
Snowflake AI Escapes Sandbox and Executes Malware
1–10 of 109 posts
Re: Snowflake AI Escapes Sandbox and Executes Malware
#2I expected this to be about gaining os privileges.
They didn't create a sandbox. Poor security design all around
Re: Snowflake AI Escapes Sandbox and Executes Malware
#3If the user has access to a lever that enables accesss, that lever is not providing a sandbox. I expected this to be about gaining os privileges. They didn't create a sandbox. Poor security design all around
Re: Snowflake AI Escapes Sandbox and Executes Malware
#4Re: Snowflake AI Escapes Sandbox and Executes Malware
#5Re: Snowflake AI Escapes Sandbox and Executes Malware
#6[flagged]
Re: Snowflake AI Escapes Sandbox and Executes Malware
#7another prompt injection (shocked pikachu)
anyways, from reading this, i feel like they (snowflake) are misusing the term "sandbox". "Cortex, by default, can set a flag to trigger unsandboxed command execution." if the thing that is sandboxed can say "do this without the sandbox", it is not a sandbox.
Re: Snowflake AI Escapes Sandbox and Executes Malware
#8Am I crazy or does this mean it didn't really escape, it wasn't given any scope restrictions in the first place ?
Re: Snowflake AI Escapes Sandbox and Executes Malware
#9If the user has access to a lever that enables accesss, that lever is not providing a sandbox. I expected this to be about gaining os privileges. They didn't create a sandbox. Poor security design all around
[flagged]
Re: Snowflake AI Escapes Sandbox and Executes Malware
#10> Note: Cortex does not support ‘workspace trust’, a security convention first seen in code editors, since adopted by most agentic CLIs. Am I crazy or does this mean it didn't really escape, it wasn't given any scope restrictions in the first place ?
>Cortex, by default, can set a flag to trigger unsandboxed command execution. The prompt injection manipulates the model to set the flag, allowing the malicious command to execute unsandboxed.
>This flag is intended to allow users to manually approve legitimate commands that require network access or access to files outside the sandbox.
>With the human-in-the-loop bypass from step 4, when the agent sets the flag to request execution outside the sandbox, the command immediately runs outside the sandbox, and the user is never prompted for consent.
scope restrictions are in place but are trivial to bypass