avo is vulnerable to Insecure Direct Object Reference (IDOR)
81
High Risk
The AttachmentsController#destroy endpoint in the Avo admin framework authorizes the delete policy against the parent record taken from the URL but then resolves the attachment through a global, unscoped ActiveStorage::Attachment.find on the user-supplied attachment ID. An authenticated user who holds delete permission on any single record can pass that check and then supply a different record's attachment ID. This permanently destroys Active Storage attachments belonging to other records, models, and tenants. The fix validates the attachment name and scopes the lookup to the authorized record's association before destroying it.
You are affected if you are using a version within the vulnerable range and if your application mounts Avo's admin interface with Active Storage attachments and grants users delete permission on any record.
avo is vulnerable to Insecure Direct Object Reference (IDOR) in versions 2.0.0 - 3.32.1 and 4.0.0 - 4.1.4.
Upgrade the avo library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant