chore(deps): update dependency carrierwave to v2.2.6 [security] #403
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.2.2
->2.2.6
GitHub Vulnerability Alerts
CVE-2023-49090
Impact
CarrierWave::Uploader::ContentTypeAllowlist 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 ofallowlisted_content_type?
is passed a value crafted by the attacker, Content-Types not included in thecontent_type_allowlist
will be allowed.In addition, by setting the Content-Type configured by the attacker at the time of file delivery, it is possible to cause XSS on the user's browser when the uploaded file is opened.
Patches
Upgrade to 3.0.5 or 2.2.5.
Workarounds
When validating with
allowlisted_content_type?
in CarrierWave::Uploader::ContentTypeAllowlist , forward match(\A
) the Content-Type set incontent_type_allowlist
, preventing unintentional permission oftext/html;image/png
when you want to allow onlyimage/png
incontent_type_allowlist
.References
OWASP - File Upload Cheat Sheet
CVE-2024-29034
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
.References
OWASP - File Upload Cheat Sheet
Release Notes
carrierwaveuploader/carrierwave (carrierwave)
v2.2.6
: 2.2.6Compare Source
Security
v2.2.5
: 2.2.5Compare Source
Security
v2.2.4
: 2.2.4Compare Source
Fixed
v2.2.3
: 2.2.3Compare Source
Fixed
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/Amsterdam, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.