Critical Rails flaw lets unauthenticated attackers write files via crafted ImageMagick uploads
Apps are exposed only if their ImageMagick policy does not already block the risky coders, which Rails says is true of the Debian and Ubuntu defaults.
Rails has patched a critical Active Storage flaw, rated 9.8 by its maintainers, that lets an unauthenticated attacker write arbitrary files to a server when an app runs uploads through ImageMagick. Attaching a crafted upload is enough to trigger it, and where the Disk service is used the attacker can also read server files, potentially including secret_key_base and stored credentials. Fixed releases are 8.1.4.1 and 8.0.5.2, which ship an ImageMagick policy blocking the risky coders. The exposure depends on the app's configuration, since apps whose ImageMagick policy already blocks these coders are not exposed, and Rails states that the Debian and Ubuntu policies do not block them. Rails says it knows of one attack chain but does not assume it is the only one, and it has not said whether the flaw has been exploited.
Why it matters
The flaw sits in a common file-upload path, so any site that accepts user images through Active Storage with ImageMagick may be reachable without logging in. Operators on Debian or Ubuntu defaults fall into the exposed group, while apps with a stricter ImageMagick policy are not. Because Rails knows of one attack chain but does not assume it is the only one, and has not said whether it has been exploited, the practical step for affected operators is to upgrade to 8.1.4.1 or 8.0.5.2 and check their ImageMagick policy.
Matters or hype?
Does this story matter, or is it hype? Vote before you see what everyone else said.