Skip to content

← Public intelligence

RubyGems package

spree_auth_devise

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratedRubyGemsPublished

    spree_auth_devise allows remote authenticated users to assign themselves arbitrary roles

    CVE-2013-2506 · GHSA-jp57-9j37-5476

    Affected
    • RubyGems spree_auth_devise >= 1.0.0, < 3.0.5
    Fixed in
    3.0.5· Vendor fix available
    Issue
    app/models/spree/user.rb in spreeauthdevise in Spree 1.1.x before 1.1.6, 1.2.x, and 1.3.x does not perform mass assignment safely when updating a user, which allows remote authenticated users to assign arbitrary roles to themselves.

    Recommended action: Upgrade to 3.0.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Critical, CVSS 9.3RubyGemsPublished

    Spree Auth Devise vulnerability allows for authentication bypass through CSRF weakness

    CVE-2021-41275 · GHSA-26xx-m4q2-xhq8

    Affected
    • RubyGems spree_auth_devise >= 4.3.0, < 4.4.1; >= 4.2.0, < 4.2.1; >= 4.1.0, < 4.1.1; < 4.0.1
    Fixed in
    4.2.14.4.14.1.14.0.1· Vendor fix available
    Issue
    Impact CSRF vulnerability that allows user account takeover. All applications using any version of the frontend component of spreeauthdevise are affected if protectfromforgery method is both: Executed whether as: A beforeaction callback (the default) A prependbeforeaction (option prepend: true given) before the :loadobject hook in Spree::UserController (most likely order to find). Configured to use :nullsession or :resetsession strategies (:nullsession is the default in case the no strategy is given, but rails --new generated skeleton use :exception). That means that applications that haven't been configured differently from what it's generated with Rails aren't affected. Thanks @waiting-for-dev for reporting and providing a patch 👏 Patches Spree 4.3 users should update to spreeauthdevise 4.4.1 Spree 4.2 users should update to spreeauthdevise 4.2.1 Spree 4.1 users should update to spreeauthdevise 4.1.1 Older Spree version users should update to spreeauthdevise 4.0.1 Workarounds If…

    Recommended action: Upgrade to 4.4.1, 4.2.1, 4.1.1 or 4.0.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →