همهٔ گزارش‌ها
زیاد

Action Pack: Possible Strong Parameters Bypass in Parameters#each_key

متن اصلی

نسخه‌های متأثر

RubyGemsactionpack
نسخه‌های متأثر
>= 8.1.0.beta1, < 8.1.4.1
نسخهٔ اصلاح‌شده
8.1.4.1
RubyGemsactionpack
نسخه‌های متأثر
< 8.0.5.2
نسخهٔ اصلاح‌شده
8.0.5.2

بهره‌برداری

CVE-2026-126081

احتمال بهره‌برداری در ۳۰ روز آینده: 0.63%

FIRST EPSS · ۱۴۰۵/۰۸/۲۸

شرح آسیب‌پذیری

Impact

ActionController::Parameters#each_key delegates to the internal ActiveSupport::HashWithIndifferentAccess that holds the request parameters, so when called with a block it returns that hash instead of the Parameters instance. The hash does not respond to permitted?, so Active Model mass assignment (new, assign_attributes, update) accepts it without raising ActiveModel::ForbiddenAttributesError. An application that passes the return value of each_key to mass assignment could allow a remote, unauthenticated attacker to set attributes that the application does not permit, such as an authorization flag.

This is an incomplete fix of CVE-2020-8164, which made each, each_pair and each_value return the Parameters instance but left each_key delegated.

Details

The fixed releases define Parameters#each_key to yield each key and return the Parameters instance when given a block, as each, each_pair and each_value do, and to return an Enumerator without one. Code that used the return value of each_key as a hash now receives the Parameters instance, which mass assignment rejects unless it is permitted.

Affected applications

An application is affected if it passes the return value of ActionController::Parameters#each_key, called with a block, to mass assignment. Rails itself makes no such call.

Workarounds

Do not use the return value of each_key. Call it for its block only, and pass the permitted Parameters instance to mass assignment.

Releases

The fixed releases are available at the normal locations.

Patches for those who cannot upgrade at once:

Versions affected
  • actionpack < 8.0.5.2

  • actionpack >= 8.1, < 8.1.4.1

Credit

This issue was responsibly reported by HackerOne researcher smlee.

پیوندها