Vulnerability GHSA-xr9x-r78c-5hrm

Critical

3 months ago

Active Storage has possible arbitrary file read and remote code execution in Active Storage variant processing

0.1 and 5.2.0.beta1 and 5.2.0.beta2 and 5.2.0.rc1 and 5.2.0.rc2 and 5.2.0 and 5.2.1.rc1 and 5.2.1 and 5.2.1.1 and 5.2.2.rc1 and 5.2.2 and 5.2.2.1 and 5.2.3.rc1 and 5.2.3 and 5.2.4.rc1 and 5.2.4 and 5.2.4.1 and 5.2.4.2 and 5.2.4.3 and 5.2.4.4 and 5.2.4.5 and 5.2.4.6 and 5.2.5 - 5.2.6 and 5.2.6.1 and 5.2.6.2 and 5.2.6.3 and 5.2.7 and 5.2.7.1 and 5.2.8 and 5.2.8.1 and 6.0.0.beta1 and 6.0.0.beta2 and 6.0.0.beta3 and 6.0.0.rc1 and 6.0.0.rc2 and 6.0.0 and 6.0.1.rc1 and 6.0.1 and 6.0.2.rc1 and 6.0.2.rc2 and 6.0.2 and 6.0.2.1 and 6.0.2.2 and 6.0.3.rc1 and 6.0.3 and 6.0.3.1 and 6.0.3.2 and 6.0.3.3 and 6.0.3.4 and 6.0.3.5 and 6.0.3.6 and 6.0.3.7 and 6.0.4 and 6.0.4.1 and 6.0.4.2 and 6.0.4.3 and 6.0.4.4 and 6.0.4.5 and 6.0.4.6 and 6.0.4.7 and 6.0.4.8 and 6.0.5 and 6.0.5.1 and 6.0.6 and 6.0.6.1 and 6.1.0.rc1 and 6.1.0.rc2 and 6.1.0 - 6.1.2 and 6.1.2.1 and 6.1.3 and 6.1.3.1 and 6.1.3.2 and 6.1.4 and 6.1.4.1 and 6.1.4.2 and 6.1.4.3 and 6.1.4.4 and 6.1.4.5 and 6.1.4.6 and 6.1.4.7 and 6.1.5 and 6.1.5.1 and 6.1.6 and 6.1.6.1 and 6.1.7 and 6.1.7.1 and 6.1.7.2 and 6.1.7.3 and 6.1.7.4 and 6.1.7.5 and 6.1.7.6 and 6.1.7.7 and 6.1.7.8 and 6.1.7.9 and 6.1.7.10 and 7.0.0.alpha1 and 7.0.0.alpha2 and 7.0.0.rc1 and 7.0.0.rc2 and 7.0.0.rc3 and 7.0.0 - 7.0.2 and 7.0.2.1 and 7.0.2.2 and 7.0.2.3 and 7.0.2.4 and 7.0.3 and 7.0.3.1 and 7.0.4 and 7.0.4.1 and 7.0.4.2 and 7.0.4.3 and 7.0.5 and 7.0.5.1 and 7.0.6 - 7.0.7 and 7.0.7.1 and 7.0.7.2 and 7.0.8 and 7.0.8.1 and 7.0.8.2 and 7.0.8.3 and 7.0.8.4 and 7.0.8.5 and 7.0.8.6 and 7.0.8.7 and 7.0.10 and 7.1.0.beta1 and 7.1.0.rc1 and 7.1.0.rc2 and 7.1.0 - 7.1.3 and 7.1.3.1 and 7.1.3.2 and 7.1.3.3 and 7.1.3.4 and 7.1.4 and 7.1.4.1 and 7.1.4.2 and 7.1.5 and 7.1.5.1 and 7.1.5.2 and 7.1.6 and 7.2.0.beta1 and 7.2.0.beta2 and 7.2.0.beta3 and 7.2.0.rc1 and 7.2.0 - 7.2.1 and 7.2.1.1 and 7.2.1.2 and 7.2.2 and 7.2.2.1 and 7.2.2.2 and 7.2.3 and 7.2.3.1 and 8.0.0.beta1 and 8.0.0.rc1 and 8.0.0.rc2 and 8.0.0 and 8.0.0.1 and 8.0.1 - 8.0.2 and 8.0.2.1 and 8.0.3 - 8.0.4 and 8.0.4.1 and 8.0.5 and 8.1.0.beta1 and 8.1.0.rc1 and 8.1.0 - 8.1.2 and 8.1.2.1 and 8.1.3

Summary

Active Storage has possible arbitrary file read and remote code execution in Active Storage variant processing

Details

Impact

In its default configuration, a Rails application that displays image variants may allow an unauthenticated attacker to read arbitrary files from the server, including the process environment. That environment typically holds secret_key_base and often credentials for external systems, which may in turn allow escalation to remote code execution or lateral movement to those systems.

Details

libvips reads and writes file formats through "loaders" and "savers" (or more generally "operations"), many of which are backed by third-party libraries. It marks some of these operations as "unfuzzed", meaning they are unsafe for untrusted content, and several handle formats unrelated to web images. Active Storage did not disable the unfuzzed operations, so an attacker who can upload a crafted file and cause a variant to be generated from it may be able to invoke one.

We are aware of a mechanism by which an attacker, by uploading a crafted file, is able to cause disclosure of the contents of arbitrary files accessible on the filesystem of the targeted application. One specific attack chain has been reported to us (see "Disclosure" below), but we do not assume it is the only one that exists.

Affected applications

An application is affected if it meets all of these requirements:

Uses libvips for Active Storage image processing. This is config.active_storage.variant_processor = :vips, which load_defaults 7.0 set and no later default has changed.
Allows image uploads from untrusted users.

Generating variants is not a separate requirement.

Mitigation

Upgrade to a fixed version of activestorage.
The minimum version of libvips must be upgraded to >= 8.13.
Change secret_key_base and change any secrets accessible in the application environment (see "Expire and change secrets" below)

Earlier versions of libvips (< 8.13) cannot disable unfuzzed operations at all, and Active Storage will raise an exception during boot in such an unsecurable environment.

Expire and change secrets

Upgrading closes the vulnerability but does not undo an exfiltrated secret if that already occurred. An affected application should treat every secret readable by the application process as potentially exposed and change it, including:

secret_key_base
The master key, whether stored in config/master.key or supplied as RAILS_MASTER_KEY, along with everything in config/credentials.yml.enc that it decrypts
Credentials for the Active Storage service, such as S3, GCS, or Azure keys
Database credentials
Tokens and keys for any third-party service the application calls

Changing secret_key_base expires active sessions and requires users to log in again. Encrypted cookies, signed cookies, signed global IDs, and Active Storage URLs are also affected.

Rotation should only be used as an intermediate step if necessary. Do not retain an exposed secret as a fallback.

Workarounds

If libvips < 8.13 is being used, there are no workarounds available other than removing the dependency on libvips from the application. Some applications may have ruby-vips declared as a dependency only for image analysis, and those applications may be able to simply remove ruby-vips from the Gemfile to remove libvips from the application. Applications that do not use Active Storage can remove ruby-vips from the Gemfile to avoid the boot-time checks.

If libvips >= 8.13 is present on the system, applications can disable the unfuzzed operations without upgrading Rails by setting the VIPS_BLOCK_UNTRUSTED environment variable, which libvips reads while initializing.

Applications also running ruby-vips >= 2.2.1 or later can instead call Vips.block_untrusted(true) from an initializer.

Releases

The fixed releases are available at the normal locations.

Versions affected

activestorage < 7.2.3.2
activestorage >= 8.0, < 8.0.5.1
activestorage >= 8.1, < 8.1.3.1

Disclosure

Technical details of the attack chain are intentionally omitted from this advisory. They would add nothing to an administrator's decision to upgrade, while making it substantially easier to attack applications that have not yet done so.

Details will be disclosed no later than 2026-08-28, via the Rails Security Announcements forum.