Security Bug about devise-two-factor HOT 8 CLOSED

Hi! I'm not sure what there is for us to do here...

from devise-two-factor.

Awaiting #43 I guess?

from devise-two-factor.

Ah. You already have a PR regarding this? As I am the co-maintainer of the debian package, I forwarded the bug to the upstream (here). Sorry for the redundancy. :)

I just saw that @f3ndot was the guy who actually requested that CVE. ;)

from devise-two-factor.

No problem, thanks for the update! We'll push out a new release once the PR is done.

from devise-two-factor.

@balasankarc, I noticed that you marked the severity as 'grave,' which it probably shouldn't be. While a valid security issue, this is a very narrow vulnerability, as described by @f3ndot himself. :)

from devise-two-factor.

Ah. It wasn't me who filed that bug (and marked it grave). The guy marked that is part of Debian Seciruty team I believe. Anyway, that is not big a deal right now as we are not looking for another Debian release anytime soon. Once that PR gets done, we can close that bug. Till then it is highly unlikely to affect anybody.

I packaged the gem for the on going GitLab packaging and I am pretty sure no one is affected by it having a grave severity. :)

from devise-two-factor.

@balasankarc fix is merged & released in 2.0.0 and the issue has been assigned CVE-2015-7225, OSVDB pending.

from devise-two-factor.

Thanks. I've updated the Debian package. :)

from devise-two-factor.