Vulnerability in carrierwave (CVE-2021-21305)
Summary
Vulnerability in carrierwave (CVE-2021-21305). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.1.1 or later.
Original description
The description as published by the source.
Impact
CarrierWave::RMagick has a Code Injection vulnerability. Its #manipulate! method inappropriately evals the content of mutation option(:read/:write), allowing attackers to craft a string that can be executed as a Ruby code.
If an application developer supplies untrusted inputs to the option, it will lead to remote code execution(RCE).
(But supplying untrusted input to the option itself is dangerous even in absence of this vulnerability, since is prone to DoS vulnerability - attackers can try to consume massive amounts of memory by resizing to a very large dimension)
Proof of Concept
class MyUploader < CarrierWave::Uploader::Base
include CarrierWave::RMagick
end
MyUploader.new.manipulate!({ read: { density: "1 }; p 'Hacked'; {" }}) # => shows "Hacked"
Patches
Workarounds
Stop supplying untrusted input to #manipulate!'s mutation option.
References
Code Injection Software Attack
For more information
If you have any questions or comments about this advisory:
- Open an issue in CarrierWave repo
- Email me at mit.shibuya@gmail.com
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-21305 has been found in carrierwave.
Risk of unauthorized operations or information disclosure.
What to do: upgrade carrierwave to 2.1.1 or later.
If unsure, ask your IT team or search "carrierwave CVE-2021-21305" on the vendor's site.
CVE-2021-21305 (carrierwave) — CWE-74
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.1.1 — apply immediately
Workaround: Stop supplying untrusted input to #manipulate!'s mutation option.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-74) exists in carrierwave.
Check the vendor advisory for the affected versions of carrierwave.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.1.1.
Workaround: Stop supplying untrusted input to #manipulate!'s mutation option.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'carrierwave' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'carrierwave' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
carrierwaveを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Stop supplying untrusted input to `#manipulate!`'s mutation option.パッチが適用されるまでの応急処置として、Stop supplying untrusted input to
#manipulate!'s mutation option. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade carrierwave to 2.1.1ステージング環境で 2.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2021-21305 ruby-carrierwave Fixed in: 1.3.2-1
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web rubygems.org