239
Malicious VSCode extensions with millions of installs discovered
(www.bleepingcomputer.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Jun 2024
239 points (94.8% liked)
Programming
17314 readers
33 users here now
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
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
I think that's how themes are distributed for VSCode, right?
With VSCode, everything is an extension.
But the vscode marketplace seems to have filters for themes, so there must be some way to differentiate them.
I think extensions need a permissions system
You declare it in the package.json as a category when publishing. It's completely self-selected with no oversight, review, or enforced permissions.
Microsoft security practices haven't changed much over the decades
You can install themes directly from the theme selector.
Even worse, it also previews the theme when selected. I hope that the logic they use for that feature works in a simpler way.
I checked the logic and there is no rce.