Carrierwave
Approved changes feed: RSS · Atom
cpe:2.3:a:carrierwaveuploader:carrierwave:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Carrierwaveuploader (4fa7490b-2b6b-5070-b20c-fb1670736275) |
|---|---|
| Product | Carrierwave (46bf64ea-47ab-5a72-b09b-5802d3551fc3) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-44587 |
vulnerable | 2026-07-29 00:52:14.471215 |
CarrierWave has a denylisted_content_type bypass via Unescaped Regex Metacharacters
MEDIUM (4.7)
CarrierWave is a framework to upload files from Ruby applications. In versions prior to 2.2.7 and 3.1.3, the content_type_denylist check fails to escape regex metacharacters in string entries, causing the denylist to silently not match the content types it is intended to block. In lib/carrierwave/uploader/content_type_denylist.rb:57, denylist entries are interpolated directly into a regex without Regexp.quote or anchoring, so an entry such as image/svg+xml becomes the pattern /image\/svg+xml/, in which + is treated as a quantifier rather than a literal character and therefore never matches the real MIME type image/svg+xml. This is inconsistent with the allowlist implementation, which correctly applies both Regexp.quote and a \A anchor. Other content types containing regex metacharacters, such as application/xhtml+xml, are affected as well. As a result, any application that relies on content_type_denylist to block image/svg+xml, most commonly to prevent stored XSS, is silently unprotected. An attacker can upload an SVG file containing arbitrary JavaScript; if the application serves that SVG inline from its own origin, the script executes in the victim's browser, resulting in stored XSS. This issue has been fixed in versions 2.2.7 and 3.1.3.
Published: 2026-06-16T23:10:43.665Z
Updated: 2026-06-17T18:12:37.182Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-29034 |
vulnerable | 2026-06-08 06:33:28.456025 |
CarrierWave's Content-Type allowlist bypass vulnerability which possibly leads to XSS remained
MEDIUM (6.8)
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.
Published: 2024-03-24T19:27:35.996Z
Updated: 2024-08-02T01:03:51.518Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-49090 |
vulnerable | 2026-06-08 06:14:28.407865 |
CarrierWave has a content-type allowlist bypass vulnerability, possibly leading to XSS
MEDIUM (6.8)
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 of `allowlisted_content_type?` is passed a value crafted by the attacker, Content-Types not included in the `content_type_allowlist` will be allowed. This issue has been patched in versions 2.2.5 and 3.0.5.
Published: 2023-11-29T14:38:52.195Z
Updated: 2024-10-11T17:55:40.314Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21305 |
vulnerable | 2026-06-08 05:29:11.584960 |
Code Injection vulnerability in CarrierWave
HIGH (7.4)
CarrierWave is an open-source RubyGem which provides a simple and flexible way to upload files from Ruby applications. In CarrierWave before versions 1.3.2 and 2.1.1, there is a code injection vulnerability. The "#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). This is fixed in versions 1.3.2 and 2.1.1.
Published: 2021-02-08T19:20:14.000Z
Updated: 2024-08-03T18:09:15.001Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-21288 |
vulnerable | 2026-06-08 05:29:11.516909 |
Server-side request forgery in CarrierWave
MEDIUM (4.3)
CarrierWave is an open-source RubyGem which provides a simple and flexible way to upload files from Ruby applications. In CarrierWave before versions 1.3.2 and 2.1.1 the download feature has an SSRF vulnerability, allowing attacks to provide DNS entries or IP addresses that are intended for internal use and gather information about the Intranet infrastructure of the platform. This is fixed in versions 1.3.2 and 2.1.1.
Published: 2021-02-08T19:15:16.000Z
Updated: 2024-08-03T18:09:15.747Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.