Skip to content

CSRF allows attacker to finalize/unfinalize order adjustments in solidus_backend

Low severity GitHub Reviewed Published Jun 1, 2022 in solidusio/solidus • Updated May 4, 2023

Package

bundler solidus_backend (RubyGems)

Affected versions

< 2.11.16
>= 3.0.0, < 3.0.6
>= 3.1.0, < 3.1.6

Patched versions

2.11.16
3.0.6
3.1.6

Description

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 GET request 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

For more information

If you have any questions or comments about this advisory:

References

@waiting-for-dev waiting-for-dev published to solidusio/solidus Jun 1, 2022
Published by the National Vulnerability Database Jun 1, 2022
Published to the GitHub Advisory Database Jun 1, 2022
Reviewed Jun 1, 2022
Last updated May 4, 2023

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.070%
(31st percentile)

Weaknesses

CVE ID

CVE-2022-31000

GHSA ID

GHSA-8639-qx56-r428

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.