3 ms·
Question from a non-Drupal dev here: this notice deals with third-party modules that don't sound like they'd be ubiquitous for deployments. But it's in the PSA
by danso 10y ago
Question from a non-Drupal dev here: this notice deals with third-party modules that don't sound like they'd be ubiquitous for deployments. But it's in the PSA section in which has few posts overall, and seems to focus on Drupal core. Am I underestimating the install base, or overestimating the likelihood of 3rd-party modules having security holes?
(It doesn't seem that WordPress's security section concerns itself with plugin flaws...because if it did, that's be a pretty busy section...)
Edit: Ok this I was also wondering: are these flaws a result of something related to Drupal core?
https://news.ycombinator.com/item?id=12088471 https://news.ycombinator.com/item?id=12088471
Is it standard for Drupal to not disable web access to disabled plugins? Or is this notice for the rare edge custom deployments in which default safeguards are disabled? How can a non-admin reach a disabled plugin (nevermind execute it)?
- ksenzee 10y agoI think the confusion here is that there are three types of advisories: Core issues, contrib issues, and PSAs. You're probably looking at yesterday's PSA saying "watch out for an important advisory tomorrow" and wondering why there aren't more advisories. It's because they're in the other two sections. It is certainly standard for code in disabled plugins not to be accessible via Drupal. The problem in this case is that the plugin's authors wrote a separate script having nothing to do with Drupal itself, and made it web-accessible. That's pretty unusual for contributed code.
- pfg 10y agoNew(ish) projects using popular PHP frameworks typically have all their code stored somewhere outside of the web server's document root - there's usually just a single PHP file in the document root that's responsible for instantiating a front controller or bootstrapping the app in some other way, with a .htaccess (or similar) file telling the web server to redirect all requests to that file. Drupal (and WordPress, etc.) come from a time where your entire code base would live in the document root, so knowing the path to a .php file is often enough to execute the script. While it would be possible to limit this with something like .htaccess, it's error-prone, web server-specific, and can break existing code in your ecosystem, so that's probably why it's not being done consistently. Changing the code structure of Drupal in a way that would put most of the code outside of the document root would similarly cause a lot of work for the ecosystem and might make installation in typical shared web hosting environments impossible in some scenarios - I've seen hosters who only allow you to upload files straight to the document root, so there'd be no way to use such a project with those plans. This is in essence just another case of things going wrong because compatibility was prioritized over possible security concerns, and I don't even want to blame them too much for that, given the usual outcry when backwards-incompatible changes cause work for (plugin) developers in general.