Live data from Hacker News

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

parsiya.net

61–70 of 109 posts

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

#61
The "Your editor has DRM" section alone [0] is enough for me to continue to advocate for a better user-friendly FOSS IDE, in addition to the wonderful giants of emacs & vim, and to avoid the VS Code "kool aid".

[0] https://parsiya.net/blog/2021-12-20-rce-in-visual-studio-cod...

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

#62
post #44

Earlier quoted context omitted.

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.

I do agree that bug bounties are too small, but isn't selling bugs on the black market illegal? I would much rather get $40 dollars for a bug and some public acknowledgement (which I could use to get a better paying job) than to sell it for criminal use.

The legal/ethical question is important, but I was just stressing OP's point about the disparity between bug bounties and what the actual exploits are worth. IANAL, but for the specific cases I mentioned (nation states and vendors who work with them), I think the legal aspect would be very different from selling it to regular black market cybercriminals (I used the generic "black market" in the first part of the original comment but I was mostly talking about those two cases).

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

#63
post #48
post #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.

No, JavaScript running in your browser can connect to it. No remote access required. Of course, if you do allow remote access it is even worse.

Wait, the browser allows random http connections to localhost from JS fetched from any domain??

Edit: after reading tfa, it appears: no it can't , but it may due to browser security vulnerabilities.

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

#64

What is the best alternative for TypeScript development? My favorite light-weight editor is Kakoune, but it really doesn't have enough plugins for the kind of work I do.

Probably one of the JetBrains products, e.g. WebStorm or IDEA.

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

#65

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?

I've been trying several editors, but VSC has the best integrated debugging, after Visual Studio itself - I use the free Visual Studio Community version. I'm primarily a C++ developer, but over the last 6 month have been doing a deep dive on machine learning with Python, and that is why I even bothered with VSC. The available guidance on setting up a Python development environment in VSC is abundant, while the same in Visual Studio IDE is significantly less, with scant troubleshooting support. I tried Visual Studio IDE for my Python work at first, but switched to VSC after issues.

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

#66
post #19

Earlier quoted context omitted.

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…

This already here, but made with a subdomain that CNAMEs to a tracker domain:

https://arxiv.org/abs/2102.09301

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

#67

I'd have taken a trip down to Buenos Aires and sold it.

I am not 100% sure, but wouldn't that be a crime under the laws of many countries? If someone left their car unlocked with keys next to your house. Will you also steal it and sell it to somebody?

The crime here would be more along the lines of selling the information that you leave your car unlocked with the keys next to your house.

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

#68
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

... Or images? I suppose one might enforce a draconian same-origin policy.. But that would no longer be "the web" I think.

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

#69
post #27
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…

What if browsers learned to connect to Unix sockets? And windows named pipes? And users could control these endpoints by the usual filesystem permissions? One can dream.

Isn't this more or less the idea behind plan 9?

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

#70
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.

Make bug bounties pay $250k and people will have their friend inside add some bugs for the outsider to find, and share the payday.

Pay-per-bug-found incentivises plenty of counterproductive things as well, especially if we're talking about people who happily sell to anyone on the black market.

Post reply on HN