Live data from Hacker News

RCE in Visual Studio Code's Remote WSL for Fun and Negative Profit

parsiya.net

31–40 of 109 posts

Re: RCE in Visual Studio Code's Remote WSL for Fun and Negative Profit

#31

I've only been using VSC for about 6 months. During my the first week of use, I noted how insecure all the plugins and their communications with the main application were set up. Dismayed, I moving the workstation to an airgapped portion of my environment, and the piece of shit would not work without a net connection. So I use VCE inside a VM now. My career includes working for security companies with sensitive infor…

Why not just use some other editor?

Re: RCE in Visual Studio Code's Remote WSL for Fun and Negative Profit

#33
post #18
post #5

Issues like this have been repeated countless times in various IDEs, debugger interfaces and local services using browser as UI. Developers need to stop using network sockets as IPC channels for local services unless browsers significantly increase the restrictions on cross site requests. Similar situation with regular CSRF attacks. And it needs to be opt out not opt in. As long it's a responsibility of developer to…

> Browsers need to stop connecting to anything other than what's typed into the navigation bar. Yes, indeed!

A web browser that doesn’t support links isn’t much of a web browser

Re: RCE in Visual Studio Code's Remote WSL for Fun and Negative Profit

#34

I've only been using VSC for about 6 months. During my the first week of use, I noted how insecure all the plugins and their communications with the main application were set up. Dismayed, I moving the workstation to an airgapped portion of my environment, and the piece of shit would not work without a net connection. So I use VCE inside a VM now. My career includes working for security companies with sensitive infor…

Why not just use some other editor?

Sounds like he has. VCE, Visual Studio Enterprise

Re: RCE in Visual Studio Code's Remote WSL for Fun and Negative Profit

#35

> Does it fix the issues? Yes. > Do I think there are other security issues here and we can bypass this? Also, yes. > Do I want to spend more time doing free work for a company with a 2.5 TRILLION market cap? Hell, no. Troubling.

Not really all that troubling, all the author is saying is that he wants to get paid for their work.

Either Microsoft or other future vendors can actually honor an established bug bounty program, or the author can sell his findings to the highest bidder. Or the author can simply not spend time and energy finding bugs in the first place.

Re: RCE in Visual Studio Code's Remote WSL for Fun and Negative Profit

#36
post #33
post #18

Earlier quoted context omitted.

> Browsers need to stop connecting to anything other than what's typed into the navigation bar. Yes, indeed!

A web browser that doesn’t support links isn’t much of a web browser

Explicitly clicking on a link is almost like typing it in the url bar, so that can be an exception

Re: RCE in Visual Studio Code's Remote WSL for Fun and Negative Profit

#37
If I'm reading this right, it assumes the machine's IP is publicly accessible over the internet; which I'm guessing -even with IPv6- is not the case in 99.999% of cases; who just exposes their development machine directly to the internet with a public IP?

Still bad, but not quite as bad as owning from the browser via localhost GET.

Re: RCE in Visual Studio Code's Remote WSL for Fun and Negative Profit

#38
post #19
post #18

Earlier quoted context omitted.

> Browsers need to stop connecting to anything other than what's typed into the navigation bar. Yes, indeed!

oh how i would love this future.

At this point of time, I give it 10min before we get a magic_proxy nginx module, then your script src will be /magic_proxy/www.evilthirdpary.com/slow_multi_megabyte_script.js

You can still import all nasty third parties required by marketing department, bypassing first party protections and leading to even worse security. Or maybe maintain allow lists, basically that's a Content Security Policy.

Future is now old man.

Re: RCE in Visual Studio Code's Remote WSL for Fun and Negative Profit

#39
post #28

Microsoft has the best bounty hunter program: go fuck yourself. If you find a way to take over MS accounts, or force email swaps, or even gamertag shanaigans, there is too much money to be made, there is not even a point for a bug bounty. It's like a $40 reward for returning a purse filled with $250k. I agree with OP: no more free bugs.

It's not just Microsoft. What most bug bounties pay isn't even close to the amount you can get from selling it on the black market (assuming you have the right connections). It's why selling exploits to nation states and vendors who work with them is so lucrative.

Re: RCE in Visual Studio Code's Remote WSL for Fun and Negative Profit

#40

> Does it fix the issues? Yes. > Do I think there are other security issues here and we can bypass this? Also, yes. > Do I want to spend more time doing free work for a company with a 2.5 TRILLION market cap? Hell, no. Troubling.

Not really all that troubling, all the author is saying is that he wants to get paid for their work. Either Microsoft or other future vendors can actually honor an established bug bounty program, or the author can sell his findings to the highest bidder. Or the author can simply not spend time and energy finding bugs in the first place.

Highest bidder is unethical and illegal.

But does not change the monetary reality

Post reply on HN