Snipe-IT: Cross-company asset maintenance re-parenting via API update
grokability snipe-it
grokability snipe-it
| Product | Affected | Fixed in |
|---|---|---|
| snipe/snipe-it Packagist |
|
|
Snipe-IT is an IT asset/license management system. Prior to 8.6.2, PATCH or PUT /api/v1/maintenances/{maintenance_id} checks access to the current maintenance record and asset but then fills attacker-controlled fields including asset_id without re-authorizing the newly supplied asset, allowing an authorized user to move a maintenance record onto an asset outside their company scope. This issue is fixed in version 8.6.2.
From the CVE record · GitHub_M
Before 8.6.2, Snipe-IT's maintenance API does not recheck access when an authorized user changes a maintenance record's asset_id. An authorized user can send a PATCH or PUT request to move a maintenance record onto an asset outside their company scope; no user interaction is described.
Teams running Snipe-IT or the Packagist package snipe/snipe-it before 8.6.2 should check their deployments.