Description (CNA)
Snipe-IT versions up to and including 8.6.3 contain a race condition (TOCTOU) in the consumable checkout API endpoint (POST /api/v1/consumables/{consumable_id}/checkout). The requested quantity is validated against the number of remaining units before the database transaction begins, and the transaction then creates the checkout records without locking the consumable row or re-checking availability. An authenticated user with permission to check out consumables can submit concurrent checkout requests for the same consumable so that both requests pass the availability check and succeed, over-allocating stock and driving the remaining inventory negative (e.g., a consumable with 1 remaining unit ends at -1 after two concurrent 1-unit checkouts). The issue is fixed in 8.7.0, which re-fetches the parent row under lockForUpdate inside the transaction and re-validates availability.
Affected (CNA)
| Vendor / product | Versions |
|---|---|
| grokability / snipe-it | affected 8.6.3 before 8.7.0; unaffected 8.7.0 |
CWE
CWE-362
References
- https://github.com/grokability/snipe-it/security/advisories/GHSA-x4g2-87xc-m5jm
- https://github.com/grokability/snipe-it/commit/f71806b1e0efbd3bc2b6be61994ad2a5d5d6c206
- https://www.vulncheck.com/advisories/snipe-it-8.6.3-race-condition-via-consumable-checkout
ADP enrichment
No English description supplied.