Plataformatec Devise version 4.5.0 and earlier, using the lockable module contains a CWE-367 vulnerability in The Devise::Models::Lockable class, more specifically at the #incrementfailedattempts method. File location: lib/devise/models/lockable.rb that can result in Multiple concurrent requests can prevent an attacker from being blocked on brute force attacks. This attack appear to be exploitable via Network connectivity - brute force attacks. This vulnerability appears to have been fixed in 4.6.0 and later.

Devise gem 2.2.x before 2.2.3, 2.1.x before 2.1.3, 2.0.x before 2.0.5, and 1.5.x before 1.5.4 for Ruby, when using certain databases, does not properly perform type conversion when performing database queries, which might allow remote attackers to cause incorrect results to be returned and bypass security checks via unknown vectors, as demonstrated by resetting passwords of arbitrary accounts.

Incorrect Access Control in filemethod? in lib/simpleform/formbuilder.rb; a user-supplied string is invoked as a method call

Impact For pages that build a form using user input, it is possible for an attacker to manipulate the input and send any method present in the form object. For example:

erb <%= simpleformfor @user do |f| %> <%= f.label @usersuppliedstring %> ... <% end %>

The string provided in the variable @usersuppliedstring would be invoked as a method call inside the @user object (unless the string contains any of the following: password, timezone, country, email, phone and url).

By manipulation that input, an attacker could do any of the following:

- Code execution (call actions like #destroy) - Denial of Service (by executing a computation intensive method) - Information Disclosure (check the presence of methods, leak user information)

Patches The problem was fixed in version 5.0. Although it's a major version, there should be no issues with upgrading for 4.x. The reason it was released in a major version is that the configuration SimpleForm.filemethods was deprecated in order to fix the problem.

Workarounds The issue only happens with pages that build forms based on user-provided input. If your application doesn't do that, you're not affected. A workaround is to explicitly pass which type you want for an input since the issue lies on Simple Form's automatically discovery of input types. This can be done using the as option, like the following: erb <%= form.input :avatar, as: :file %>

References [TDB]

For more information If you have any questions or comments about this advisory: Open an issue in https://github.com/plataformatec/simpleform Email us at opensource@plataformatec.com.br

An issue was discovered in Plataformatec Devise before 4.7.1. It confirms accounts upon receiving a request with a blank confirmationtoken, if a database record has a blank value in the confirmationtoken column. (However, there is no scenario within Devise itself in which such database records would exist.)