soiax

6 ms·

1.
by soiax 12d ago
The title is bad, it is not sandbox escape, it is "RCE inside the sandbox", so only RCE when sandbox is disabled.
2.
by soiax 20d ago
Why are people upvoting a unexploitable bug? How is this interesting? There are thounds of these, no one even reports them unless they are exploitable, DoS only.
3.
by soiax 1mo ago
Right, but we have no clue why, and how the emergent behavior they show works. If we would know that, there would be no need for interpretability research.
4.
by soiax 7mo ago
They should also check for hot dog vs not hot dog
5.
by soiax 8mo ago
Yeah dude .. if you say it multiple times, and louder, it must be true. That would make it a nazi company, right.
6.
by soiax 8mo ago
There it is... the usual ELON MUSK BAD.
7.
by soiax 2y ago
You mentioned prompt injection, now when you talk about larger time horizons, that sounds like a AI alignment issue. I'm sure there will be actors who don't care at all about "security", saying the positive outcomes outw
8.
by soiax 2y ago
Yeah that's false. from: https://arcprize.org/blog/oai-o3-pub-breakthrough "Note on "tuned": OpenAI shared they trained the o3 we tested on 75% of the Public Training set. They have not shared more
9.
by soiax 2y ago
This sound like you assume that the first thing someone thinks about is security, when building the next big thing. They will just build something as fast as they can. Last thing you think about is "security". There were prompt in
10.
by soiax 2y ago
You can disable it runtime, with --no-sandbox command line option.
11.
by soiax 2y ago
No. There is a reason the author keeps repeating "arbitrary code execution in the Chrome renderer process." Because it's there, not in the browser process.
12.
by soiax 2y ago
It's all renderer only RCE-s, no sandbox escape. So it doesn't work on your browser, only if you disable the sandbox.