activestorage
Affected
- introduced
8.0, fixed8.0.2.1(ecosystem)
Fixed versions
8.0.2.1
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2025-24293
Active Storage allowed transformation methods that were potentially unsafe
Active Storage attempts to prevent the use of potentially unsafe image transformation methods and parameters by default.
The default allowed list contains three methods allowing for the circumvention of the safe defaults which enables potential command injection vulnerabilities in cases where arbitrary user supplied input is accepted as valid transformation methods or parameters.
This has been assigned the CVE identifier CVE-2025-24293.
Versions Affected: >= 5.2.0
Not affected: < 5.2.0
Fixed Versions: 7.1.5.2, 7.2.2.2, 8.0.2.1
Impact
------
This vulnerability impacts applications that use Active Storage with the image_processing processing gem in addition to mini_magick as the image processor.
Vulnerable code will look something similar to this:
<%= image_tag blob.variant(params[:t] => params[:v]) %>
Where the transformation method or its arguments are untrusted arbitrary input.
All users running an affected release should either upgrade or use one of the workarounds immediately.
Releases
--------
The fixed releases are available at the normal locations.
Workarounds
-----------
Consuming user supplied input for image transformation methods or their parameters is unsupported behavior and should be considered dangerous.
Strict validation of user supplied methods and parameters should be performed as well as having a strong ImageMagick security policy deployed.
Credits
-------
Thank you lio346 from Unit 515 of OPSWAT for reporting this!
Critical Basis: The source's own band: CRITICAL
8.0, fixed 8.0.2.1 (ecosystem)8.0.2.1
The export has no generic command for this ecosystem.
7.2, fixed 7.2.2.2 (ecosystem)7.2.2.2
The export has no generic command for this ecosystem.
5.2.0, fixed 7.1.5.2 (ecosystem)7.1.5.2
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0