Here's the patch that fixes the vulnerabilities (see https://www.drupal.org/node/2679541).
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | node_notify-xss_csrf_fix-2730827-6.patch | 13.84 KB | alex.bukach |
Here's the patch that fixes the vulnerabilities (see https://www.drupal.org/node/2679541).
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | node_notify-xss_csrf_fix-2730827-6.patch | 13.84 KB | alex.bukach |
Comments
Comment #2
damienmckennaIf you're able to, it might help to write some tests that confirm the XSS and CSRF vulnerabilities are fixed by the patch.
Comment #3
interx commentedFYI, when I reported this module's vulnerabilities, I created a patch for them too.
I'ts mostly similar, but fixes the tests too.
Comment #4
alex.bukach commented@interX thanks for the patch. I have merged our two patches and updated the tests.
Unfortunately your tests failed for me due to the token issue. Also as @DamienMcKenna recommended, I have added the tests to check absence of XSS (at subscriptions page, in watchdog messages and emails sent) and CSRF (403 response in the case when the token is empty or wrong) vulnerabilities.
Comment #5
klausidouble escaping, l() will already run check_plain().
double escaping, l() will already run check_plain().
return MENU_ACCESS_DENIED here instead of calling drupal_access_denied().
Comment #6
alex.bukach commented@klausi thanks for the review, makes sense!
Comment #7
alex.bukach commentedWould it be possible to review and promote this patch? Please see https://www.drupal.org/node/2730831
Comment #8
benjamin_dk commentedIs there any chance that someone with the proper privileges could take a look at this patch and make @Alex Bukach co-maintainer, so we can get the module out of "red-box" state? @DamienMcKenna maybe?
Comment #9
prat commented@benjamin_dk, I have added @Alex Bukach to co-maintainers , so now he can submit new release
Comment #10
benjamin_dk commented@prat thanks!
Comment #12
alex.bukach commentedComment #13
alex.bukach commentedNow how can we mark https://www.drupal.org/node/2679541 as resolved?
Comment #15
klausiPlease create a new release and mark it as security update, the Drupal Security Team will then publish that.
Comment #16
alex.bukach commentedThanks @klausi, done!
Comment #17
klausiHi Alex, 7.x-1.0-alpha1 is the wrong version number. The last release was 7.x-1.1, so the next release must be 7.x-1.2.
Comment #18
fabianderijkIs there any progress? I would like to use this module in a project I'm working on, and there is no release available.
Comment #19
klausiAlex Bukach has not made a 7.x-1.2 release yet, so we are waiting on that.
Comment #20
klausiContinuing in #2848833: Create 7.x-1.2 release.