solidus_backend 1.3.1
CSRF allows attacker to finalize/unfinalize order adjustments in solidus_backend
low severity CVE-2022-31000~> 2.11.16, ~> 3.0.6, >= 3.1.6
Impact
CSRF vulnerability allowing attackers to change the state of an order's adjustments if they hold its number, and the execution happens on a store administrator's computer.
Reproduction steps:
- Take an order's number.
- Log in as an administrator.
- Visit that order's adjustments section (Orders -> {Click on number} -> Adjustments) and check that its adjustments are finalized (closed padlock under the State column).
- On another tab, visit
{your_site_url}/admin/orders/{order_number}/adjustments/unfinalize. - Notice how the adjustments are unfinalized (open padlock), even if the previous was a
GETrequest which could have been linked from any other site. - Visit
{your_site_url}/admin/orders/{order_number}/adjustments/finalize. - Notice how the adjustments are again finalized.
That happened because both routes were handled as GET requests, which are skipped by Rails anti-forgery protection.
Patches
Users should upgrade to solidus_backend v3.1.6, v3.0.6, or v2.11.16, depending on the major and minor versions in use.
References
No officially reported memory leakage issues detected.
This gem version does not have any officially reported memory leaked issues.
Gem version without a license.
Unless a license that specifies otherwise is included, nobody can use, copy, distribute, or modify this library without being at risk of take-downs, shake-downs, or litigation.
This gem version is available.
This gem version has not been yanked and is still available for usage.