CarrierWave has a denylisted_content_type bypass via Unescaped Regex Metacharacters
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| carrierwaveuploader | carrierwave | affected |
|
Configuration 1 [-]
|
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Carrierwave Project | Carrierwave |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-7g26-2qgj-chfg | CarrierWave has a denylisted_content_type bypass via Unescaped Regex Metacharacters |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.223% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Carrierwave Project
Carrierwave Project carrierwave |
|
| Vendors & Products |
Carrierwave Project
Carrierwave Project carrierwave |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | CarrierWave has a denylisted_content_type bypass via Unescaped Regex Metacharacters | |
| Weaknesses | CWE-184 CWE-625 CWE-79 |
|
| References |
| |
| Metrics |
cvssV3_1
|