News for hackers. Stuff that matters.
Re:How botnets are created with hijacked Worpess, fake Flash... by lucaspiller on Monday November 23, 2015 @01:39PM (#10616306)
Over the summer I tried taking over a few abandoned Wordpress plugins, some of which had a similar number of installs. Before they would even try to get in touch with the authors they wanted to see my updated code and made sure it was up to current Wordpress standards. Once you have access to the plugin repo you are free to push whatever you want though without review...
Re:How botnets are created with hijacked Worpess, fake Flash... by Otto42 on Monday November 23, 2015 @08:25PM (#10618569)
"Without review" is not quite true. Some of us get an email for every commit. Not kidding. Helps a lot for the scanning of things.
Re:How botnets are created with hijacked Worpess, fake Flash... by lucaspiller on Tuesday November 24, 2015 @01:05AM (#10619368)
I meant more that code can be pushed to the repository without it being reviewed first, not that nobody is looking at it. If someone does push something bad are there systems in place to blacklist a plugin and remotely remove it from an install (and possibly contact the install owners)?
Re:How botnets are created with hijacked Worpess, fake Flash... by Otto42 on Tuesday November 24, 2015 @07:30AM (#10620330)
> are there systems in place to blacklist a plugin and remotely remove it from an install (and possibly contact the install owners)

We have automated scanning systems for suspicious code commits. If they occur, me and a few others get an email for manual review of the problem. Additionally, many others get every commit and set up their own scanning tools to see what's happening, as it happens.

When something-bad™ happens, then we can close a plugin (block it from being downloaded or found in searches), revert changes or otherwise manually adjust any aspect of the plugin, and if necessary, push updates for it to any WordPress installs that have it.

Realistically, bad actors are not generally a problem for the plugins system. I can count on one hand the number of times this has occurred to the point where we'd need to actually push code. The real problem we're fighting is accidental security issues. While WordPress core is quite secure, plugins have much less eyes on the problem, and a lot of plugin developers are relatively new coders. Things like simple SQL injections still pop up from time to time in plugins, and that's a big problem.

So, the security issues with with plugins repository is not really about some malicious person out there. Malicious people tend to be dumb spammers. They're easy to spot and protect against, because they're only after the low hanging fruit. What we mostly try to find are the things that good coding practices would protect against, because not everybody uses good coding practices. Those tend to be harder to scan for on an automatic basis.

Re:How botnets are created with hijacked Worpess, fake Flash... by lucaspiller on Tuesday November 24, 2015 @07:49AM (#10620383)
Thanks for the explanation, keep up the good work!