Sylius has a Promotion Usage Limit Bypass via Race Condition
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.2.3, 2.1.12, 2.0.16, 1.14.18, 1.13.15, and 4 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
Sylius is an Open Source eCommerce Framework on Symfony. A Time-of-Check To Time-of-Use (TOCTOU) race condition was discovered in the promotion usage limit enforcement. The same class of vulnerability affects the promotion usage limit (the global used counter on Promotion entities), coupon usage limit (the global used counter on PromotionCoupon entities), and coupon per-customer usage limit (the per-customer redemption count on PromotionCoupon entities). In all three cases, the eligibility check reads the used counter (or order count) from an in-memory Doctrine entity during validation, while the actual usage increment in OrderPromotionsUsageModifier happens later during order completion — with no database-level locking or atomic operations between the two phases. Because Doctrine flushes an absolute value (SET used = 1) rather than an atomic increment (SET used = used + 1), and because the affected entities lack optimistic locking, concurrent requests all read the same stale usage counts and pass the eligibility checks simultaneously. An attacker can exploit this by preparing multiple carts with the same limited-use promotion or coupon and firing simultaneous PATCH /api/v2/shop/orders/{token}/complete requests. All requests pass the usage limit checks and complete successfully, allowing a single-use promotion or coupon to be redeemed an arbitrary number of times. The per-customer limit can be bypassed in the same way by a single customer completing multiple orders concurrently. No authentication is required to exploit this vulnerability. This may lead to direct financial loss through unlimited redemption of limited-use promotions and discount coupons. The issue is fixed in versions: 1.9.12, 1.10.16, 1.11.17, 1.12.23, 1.13.15, 1.14.18, 2.0.16, 2.1.12, 2.2.3 and above.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Sylius Sylius
From 2.2.0 · fixed in 2.2.3; From 2.1.0 · fixed in 2.1.12; From 2.0.0 · fixed in 2.0.16; From 1.14.0 · fixed in 1.14.18; From 1.13.0 · fixed in 1.13.15; From 1.12.0 · fixed in 1.12.23; From 1.11.0 · fixed in 1.11.17; From 1.10.0 · fixed in 1.10.16; fixed in 1.9.12
- sylius/syliusPackagist
fixed in 1.9.12
- sylius/syliusPackagist
From 1.10.0 · fixed in 1.10.16
- sylius/syliusPackagist
From 1.11.0 · fixed in 1.11.17
- sylius/syliusPackagist
From 1.12.0 · fixed in 1.12.23
- sylius/syliusPackagist
From 1.13.0 · fixed in 1.13.15
- sylius/syliusPackagist
From 1.14.0 · fixed in 1.14.18
- sylius/syliusPackagist
From 2.0.0 · fixed in 2.0.16
- sylius/syliusPackagist
From 2.1.0 · fixed in 2.1.12
- sylius/syliusPackagist
From 2.2.0 · fixed in 2.2.3