MediumGHSA-vfmv-jfc5-pjjwCVE-2024-29034

CarrierWave content-Type allowlist bypass vulnerability which possibly leads to XSS remained

Published 25 Mar 2024 · Updated 27 Mar 2024

Is your project on an affected carrierwave?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

carrierwaveRubyGems
Affected
>=3.0.0 <3.0.7
Fixed in
3.0.7
Update to the fixed version for your release line, for example:bundle update --conservative carrierwave # Gemfile: '>= 3.0.7'
carrierwaveRubyGems
Affected
<2.2.6
Fixed in
2.2.6
Update to the fixed version for your release line, for example:bundle update --conservative carrierwave # Gemfile: '>= 2.2.6'

Details

Impact

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.

Patches

Upgrade to 3.0.7 or 2.2.6.

Workarounds

Use the following monkey patch to let CarrierWave parse the Content-type by using Marcel::MimeType.for.

# For CarrierWave 3.x
CarrierWave::SanitizedFile.class_eval do
  def declared_content_type
    @declared_content_type ||
      if @file.respond_to?(:content_type) && @file.content_type
        Marcel::MimeType.for(declared_type: @file.content_type.to_s.chomp)
      end
  end
end
# For CarrierWave 2.x
CarrierWave::SanitizedFile.class_eval do
  def existing_content_type
    if @file.respond_to?(:content_type) && @file.content_type
      Marcel::MimeType.for(declared_type: @file.content_type.to_s.chomp)
    end
  end
end

References

OWASP - File Upload Cheat Sheet

Is GHSA-vfmv-jfc5-pjjw in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected carrierwave, and gives you the command that fixes it.

More advisories for carrierwave

  • MediumCVE-2026-44587CarrierWave has a denylisted_content_type bypass via Unescaped Regex Metacharacters · 27 May 2026
  • MediumCVE-2023-49090CarrierWave Content-Type allowlist bypass vulnerability, possibly leading to XSS · 29 Nov 2023
  • HighCVE-2021-21305Code Injection vulnerability in CarrierWave::RMagick · 8 Feb 2021
  • MediumCVE-2021-21288Server-side request forgery in CarrierWave · 8 Feb 2021
carrierwave security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.