CVE-2024-29034
MediumCVSS 6.8Summary
CarrierWave did not fully address CVE-2023-49090. When uploading to object storage (e.g., Amazon S3), it is possible to set a Content-Type value that browsers interpret differently from what content_type_allowlist permits, by providing multiple comma-separated values.
Risk Assessment
Bypassing the allowed content type list can enable XSS attacks in applications using CarrierWave.
Recommendation
Upgrade CarrierWave to version 3.0.7 or 2.2.6.
Other vulnerabilities in CarrierWave
See all- CVE-2023-49090Medium
CarrierWave is a solution for file uploads for Rails, Sinatra and other Ruby web frameworks. CarrierWave has a Content-Type allowlist bypass vulnerability, possibly leading to XSS. The validation in allowlisted_content_type? determines Content-Type permissions by performing a partial match. If the content_type argument is crafted by an attacker, Content-Types not included in the allowlist will be allowed. This issue has been patched in versions 2.2.5 and 3.0.5.
- CVE-2026-44587Medium
In the CarrierWave framework, versions prior to 2.2.7 and 3.1.3, the content_type_denylist check fails to properly handle regex metacharacters in string entries, leading to intended content types not being blocked. As a result, applications may be vulnerable to XSS attacks through uploading SVG files containing malicious JavaScript.
Original NVD description (English source)
CarrierWave is a solution for file uploads for Rails, Sinatra and other Ruby web frameworks. The vulnerability CVE-2023-49090 wasn't fully addressed. This vulnerability is caused by the fact that when uploading to object storage, including Amazon S3, it is possible to set a Content-Type value that is interpreted by browsers to be different from what's allowed by `content_type_allowlist`, by providing multiple values separated by commas. This bypassed value can be used to cause XSS. Upgrade to 3.0.7 or 2.2.6.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS