Summary
Snipe-IT fails to enforce authorization on the hardware history endpoint, allowing any authenticated user to reassign assets and alter audit records. An attacker may submit crafted CSV data to move assets across companies and insert fraudulent history entries, undermining inventory integrity and accountability.
Affected context
The issue occurs in Snipe-IT deployments where authenticated users can reach the POST hardware history endpoint and the endpoint does not verify whether they are authorized to modify the targeted assets or audit records. Deployments managing assets across multiple companies may be particularly exposed because inadequate object-level and tenant-level checks can allow cross-company changes.
Exploit preconditions
- Attack surface: The authenticated POST hardware history endpoint
- Required access: A valid authenticated user account
- Trigger point: Submission of asset reassignment or history data, including CSV content
- Why exploitation is possible: The endpoint accepts state-changing requests without adequately checking the user's authorization for the selected assets, companies, or audit entries
Why this happens
The underlying flaw is a missing authorization check on a sensitive state-changing operation. Authentication establishes that a user has an account, but the endpoint does not sufficiently enforce whether that user may modify each targeted asset or append the corresponding audit record. This behavior maps to CWE-862: Missing Authorization, where access-control enforcement is absent or incomplete for a protected function.
Potential impact
- An attacker may reassign assets without the required permissions
- Asset ownership, location, or company records could be changed
- Fraudulent audit trail entries could be inserted
- Inventory reporting and accountability could be undermined
- Cross-company asset boundaries could be weakened
General mitigation guidance
Mitigation generally focuses on enforcing authorization at the endpoint and object levels rather than relying on authentication alone.
Common defensive patterns include:
- Apply server-side authorization checks to every state-changing request
- Verify permissions for each asset, company, and history record referenced by an import
- Enforce tenant and company boundaries consistently
- Use allowlisted import fields and validate records before applying changes
- Require elevated privileges for bulk reassignment and audit-sensitive operations
- Preserve audit records through controlled, append-only workflows where appropriate
- Default to denying access when authorization context is missing or ambiguous
How teams detect issues like this
Organizations can look for:
- Static analysis and code review rules requiring authorization checks on mutation endpoints
- Signals that controllers trust authenticated identity without validating target-object ownership or scope
- Tests covering cross-company access, bulk imports, and unauthorized audit changes
- Policy checks requiring object-level authorization before database updates
- Audit monitoring for unusual bulk reassignment activity or changes spanning multiple companies
Automated application-security review tools may help identify endpoints that mutate records without corresponding permission enforcement.

