Comments

Alex Bukach created an issue. See original summary.

damienmckenna’s picture

If you're able to, it might help to write some tests that confirm the XSS and CSRF vulnerabilities are fixed by the patch.

interx’s picture

StatusFileSize
new5.86 KB

FYI, when I reported this module's vulnerabilities, I created a patch for them too.
I'ts mostly similar, but fixes the tests too.

alex.bukach’s picture

StatusFileSize
new14.24 KB

@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.

klausi’s picture

Status: Needs review » Needs work
  1. +++ b/node_notify.module
    @@ -831,9 +845,9 @@ function node_notify_log($subscription, $notification, $comment, $message = NULL
    +    '!comment' => l(check_plain($comment->subject), 'comment/' . $comment->cid, array('fragment' => 'comment-' . $comment->cid)),
    

    double escaping, l() will already run check_plain().

  2. +++ b/node_notify.module
    @@ -866,7 +880,21 @@ function node_notify_log($subscription, $notification, $comment, $message = NULL
    +      '!comment' => l(check_plain($comment->subject), comment_uri($comment)),
    

    double escaping, l() will already run check_plain().

  3. +++ b/node_notify.pages.inc
    @@ -31,14 +31,17 @@ function node_notify_disable_page($token) {
    +    drupal_access_denied();
    

    return MENU_ACCESS_DENIED here instead of calling drupal_access_denied().

alex.bukach’s picture

Status: Needs work » Needs review
StatusFileSize
new1.5 KB
new13.84 KB

@klausi thanks for the review, makes sense!

alex.bukach’s picture

Would it be possible to review and promote this patch? Please see https://www.drupal.org/node/2730831

benjamin_dk’s picture

Is 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?

prat’s picture

@benjamin_dk, I have added @Alex Bukach to co-maintainers , so now he can submit new release

benjamin_dk’s picture

@prat thanks!

  • Alex Bukach committed 94d27c5 on 7.x-1.x
    Issue #2730827 by Alex Bukach, interX: Fixed XSS and CSRF...
alex.bukach’s picture

Status: Needs review » Fixed
alex.bukach’s picture

Now how can we mark https://www.drupal.org/node/2679541 as resolved?

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

klausi’s picture

Please create a new release and mark it as security update, the Drupal Security Team will then publish that.

alex.bukach’s picture

Thanks @klausi, done!

klausi’s picture

Hi 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.

fabianderijk’s picture

Is there any progress? I would like to use this module in a project I'm working on, and there is no release available.

klausi’s picture

Alex Bukach has not made a 7.x-1.2 release yet, so we are waiting on that.

klausi’s picture