Ability to change order address without triggering address validations in solidus
solidusio · solidus
In solidus before versions 2.8.6, 2.9.6, and 2.10.2, there is an bility to change order address without triggering address validations. This vulnerability allows a malicious customer to craft request data with parameters that allow changing the address of the current order without changing the shipment costs associated with the new shipment. All stores with at least two shipping zones and different costs of shipment per zone are impacted. This problem comes from how checkout permitted attributes are structured. We have a single list of attributes that are permitted across the whole checkout, no matter the step that is being submitted. See the linked reference for more information. As a workaround, if it is not possible to upgrade to a supported patched version, please use this gist in the references section.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 3/15
How an attack unfolds
Based on MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. mappings. Select a step to see the evidence.Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 4 Aug 2020. No public exploit code or confirmed exploitation is recorded.
Patch historyEarlier and later CVEs in the same code, in date order. It shows when a fix was bypassed or incomplete and which version finally fixed it.
2 fixes in solidus_frontend over 17 months. The latest fix listed for solidus_frontend is 3.1.5.
Fixes in solidus_frontendRubyGems package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.
- 2.10.2CVE-2020-151094 Aug 2020
- 3.1.5CVE-2021-4384620 Dec 2021Latest listed
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
3 TechniqueOne specific attacker behaviour in MITRE ATT&CK, such as T1190 “Exploit Public-Facing Application”. IDs with a dot, like T1059.004, are sub-techniques., grouped by TacticThe attacker’s goal at a stage of an attack in MITRE ATT&CK, such as Initial Access or Persistence. Each technique belongs to one or more tactics. in kill-chain order 3Initial AccessTA0001
ImpactTA0040
Detection
0 rules for this CVE · 172 general rules for its techniquesRules for this CVE
0Sigma ruleAn open, vendor-neutral detection rule for log data. Security teams convert Sigma rules into searches for their own SIEM. that reference CVE-2020-15109 directly.CVE-specific rules are not available in this build. Search SigmaHQ ↗
General rules for this CVE’s techniques
These detect the technique in general, not this specific vulnerability.
External Remote ServicesT113320 general rules
- External Remote SMB Logon from Public IPhightest
- OpenCanary - SSH Login Attempthightest
- OpenCanary - SSH New Connection Attempthightest
- OpenCanary - Telnet Login Attempthightest
- Running Chrome VPN Extensions via the Registry 2 VPN Extensionhightest
- Unusual Child Process of dns.exehightest
- Unusual File Deletion by Dns.exehightest
- Unusual File Modification by dns.exehightest
Exploit Public-Facing ApplicationT1190149 general rules
- Arcadyan Router Exploitationscriticaltest
- Citrix ADS Exploitation CVE-2020-8193 CVE-2020-8195criticaltest
- Citrix Netscaler Attack CVE-2019-19781criticaltest
- Confluence Exploitation CVE-2019-3398criticaltest
- CVE-2010-5278 Exploitation Attemptcriticaltest
- CVE-2020-0688 Exchange Exploitation via Web Logcriticaltest
- CVE-2020-10148 SolarWinds Orion API Auth Bypasscriticaltest
- CVE-2020-5902 F5 BIG-IP Exploitation Attemptcriticaltest
Data ManipulationT15653 general rules
Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.
Am I affected? What do I upgrade to?
From GitHub Security Advisories and OSV2 packages in 1 ecosystem. No single main package: each of these ships the affected code.
- RubyGemssolidus_frontendAffected: 2.10.0 up to 2.10.2; 2.9.0 up to 2.9.6; All versions before 2.8.6Upgrade to 2.10.2 or later (older lines: 2.9.6, 2.8.6)
- RubyGemssolidus_apiAffected: 2.10.0 up to 2.10.2; 2.9.0 up to 2.9.6; All versions before 2.8.6Upgrade to 2.10.2 or later (older lines: 2.9.6, 2.8.6)