This is the full story of the vulnerability we have discovered within Visual Studio Code (VS Code) concerning the handling of secure token storage. While designed for isolated storage for each extension, this vulnerability presents...
FYI to all the VS Code peeps out there that malicious extensions can gain access to secrets stored by other VS Code extensions as well as the tokens used by VS Code for Microsoft/Github.
I really don’t understand how Microsoft’s official stance on this is that this is working as intended…
If you weren’t already, be very careful about which extensions you are installing.
So what? Malicious extensions can do anything. Don’t run untrusted code on any computer you care about, ever. This is true for any IDE extension, any NPM package, any mod pack, etc.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
Follow the programming.dev instance rules
Keep content related to programming in some way
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
So what? Malicious extensions can do anything. Don’t run untrusted code on any computer you care about, ever. This is true for any IDE extension, any NPM package, any mod pack, etc.
JS devs looking around the room sweating over their spiderweb of NPM libraries