[Full-disclosure] Vulnerability in reCAPTCHA for Drupal
mustlive at websecurity.com.ua
Sun Feb 20 12:34:16 GMT 2011
> fucking *two days*? Is that even enough time for the vendor to
You've read inattentively - between informing of developers and disclosing
of vulnerabilities the two months and two days have passed (as you can see
in Timeline section). So be more attentive next time.
About how much time developers need to fix the holes.
1. The developers need enough time and I'm always giving them enough time.
In different cases I gave different time: sometimes it was month or few
months, sometimes it was year or even more. But always sufficient amount of
time (and if developer just ignore the hole, then regardless of given time,
such developer never fix it). In average I'm giving two months for fixing.
2. Different developers need different amount of time. It also depends on
number of vulnerabilities.
For example, developer of PHPXref fixed holes on the next day after I
informed him (http://phpxref.sourceforge.net/Changelog). And developers of
MyBB, which I informed about multiple vulnerabilities last week, they are
still investigating them (for more then week), as they stated.
Mozilla requires just ten days, as they stated
(http://ha.ckers.org/blog/20070803/mozilla-says-ten-fucking-days/). And I
had such cases, when admins of web sites fixed holes in a few minutes after
receiving of my letter (as they stated, when quickly answered me after the
So there are developers which fix holes quickly enough.
Best wishes & regards,
Administrator of Websecurity web site
----- Original Message -----
From: Zach C.
Cc: bugtraq at securityfocus.com ; full-disclosure at lists.grok.org.uk ;
submissions at packetstormsecurity.org
Sent: Thursday, February 17, 2011 7:54 PM
Subject: Re: [Full-disclosure] Vulnerability in reCAPTCHA for Drupal
fucking *two days*? Is that even enough time for the vendor to acknowledge?
On Feb 17, 2011 9:20 AM, "MustLive" <mustlive at websecurity.com.ua> wrote:
> Hello list!
> I want to warn you about Insufficient Anti-automation vulnerability in
> reCAPTCHA for Drupal.
> In project MoBiC in 2007 I already wrote about bypassing of reCaptcha for
> Drupal (http://websecurity.com.ua/1505/). This is new method of bypassing
> reCaptcha for Drupal.
> Affected products:
> Vulnerable are all versions of reCAPTCHA plugin for Captcha module
> before 6.x-2.3 and 7.x-1.0.
> Insufficient Anti-automation (WASC-21):
> In different forms in Drupal the vulnerable captcha-plugin reCAPTCHA is
> using. Drupal's Captcha module is vulnerable itself, so besides reCAPTCHA
> other captcha-plugins also can be vulnerable (at that this exploit is a
> little different from exploit for default Captcha module for Drupal).
> For bypassing of captcha it's needed to use correct value of captcha_sid,
> that it's possible to not answer at captcha (captcha_response) or set any
> answer. This method of captcha bypass is described in my project Month of
> Bugs in Captchas (http://websecurity.com.ua/1498/). Attack is possible
> this captcha_sid value is active.
> Vulnerabilities exist on pages with forms: http://site/contact,
> http://site/user/1/contact, http://site/user/password and
> http://site/user/register. Other forms where reCAPTCHA is using also will
> 2010.12.11 - announced at my site.
> 2010.12.14 - informed reCAPTCHA developers.
> 2010.12.14 - informed Google (reCAPTCHA owner).
> 2011.02.16 - disclosed at my site.
> I mentioned about this vulnerability at my site
> Best wishes & regards,
> Administrator of Websecurity web site
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
Full-Disclosure is hosted and sponsored by Secunia.