| ▲ | jnwatson 6 hours ago |
| It means it can execute arbitrary machine code in the sandbox. |
|
| ▲ | r_lee 6 hours ago | parent | next [-] |
| I think people would like to understand what the "sandbox" is here and what isolation does it provide, is it an unprivileged process? something chromium specific? a v8/JS thing? etc. |
| |
|
| ▲ | zahlman 6 hours ago | parent | prev | next [-] |
| Okay, and why is that more of a security risk than executing arbitrary JavaScript in the sandbox? |
| |
| ▲ | arcfour 5 hours ago | parent | next [-] | | Among other things, JavaScript in the browser has no way to even express "kill PID 1234 on the user's machine" or "list the contents of `C:\Users\Documents` and upload all of the files" or "spawn cmd.exe on the user's machine". How would you even do these things if you could run any JavaScript in the browser? You can't. However, chrome.exe itself does because it's a native application, as is the sandboxed JavaScript interpreter inside of chrome.exe. (This is a very oversimplified explanation but I think this is the disconnect people are having) | | |
| ▲ | bawolff 4 hours ago | parent [-] | | > JavaScript in the browser has no way to even express ... "list the contents of `C:\Users\Documents` and upload all of the files" this is besides the point, but javascript has the file system api. anyways to your broad point, i dont think this is convincing. What's the difference between not having an api vs having an api that is disabled (e.g. the syscall exists but is filtered). Either way you are not taking the action. RCE in the sandbox is an important step in the bigger exploit chain, but not because you can express things in the traditional syscalls inside the sandbox. |
| |
| ▲ | insanitybit 5 hours ago | parent | prev | next [-] | | Because Javascript theoretically can't just access files on disk. Control over the render would let you do that, if not for the process level sandbox, which constraints things like file access, system, calls, etc. But the process is still more capable than the VM. The process can talk to other processes via IPC, for example. That's why you don't go from "javascript -> computer is taken over", instead you go from "javascript -> renderer control -> computer is taken over". | |
| ▲ | r_lee 6 hours ago | parent | prev | next [-] | | because with proper code exec you can trigger other bugs to escalate beyond the sandbox, whereas with JS you'd have to find a bug to escape from JS to native can't get a proper ios/Android RCE with just JS code exec | |
| ▲ | p-e-w 5 hours ago | parent | prev [-] | | It can do some things that JS can’t do, such as invalid pointer writes. But you are correct that this doesn’t automatically imply system access. |
|
|
| ▲ | TacticalCoder 5 hours ago | parent | prev [-] |
| > It means it can execute arbitrary machine code in the sandbox. Well which is precisely why we have sandboxes. To me "executing arbitrary code in the sandbox" is similar to "I don't give a flying fuck for it's what a sandbox is for". More information is needed. As someone commented: this has to be paired with at least another exploit to make anything remotely useful. A sandbox is a sandbox. We want to understand how "code running in a sandbox" is "actively exploited". |
