Skip to content

Server-side request forgery in CarrierWave

Moderate severity GitHub Reviewed Published Feb 8, 2021 in carrierwaveuploader/carrierwave • Updated May 16, 2023

Package

bundler carrierwave (RubyGems)

Affected versions

< 1.3.2
>= 2.0.0, < 2.1.1

Patched versions

1.3.2
2.1.1

Description

Impact

CarrierWave 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.

Patches

Upgrade to 2.1.1 or 1.3.2.

Workarounds

Using proper network segmentation and applying the principle of least privilege to outbound connections from application servers can reduce the severity of SSRF vulnerabilities. Ideally the vulnerable gem should run on an isolated server without access to any internal network resources or cloud metadata access.

References

Server-Side Request Forgery Prevention Cheat Sheet

For more information

If you have any questions or comments about this advisory:

References

@mshibuya mshibuya published to carrierwaveuploader/carrierwave Feb 8, 2021
Reviewed Feb 8, 2021
Published to the GitHub Advisory Database Feb 8, 2021
Published by the National Vulnerability Database Feb 8, 2021
Last updated May 16, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.077%
(35th percentile)

Weaknesses

CVE ID

CVE-2021-21288

GHSA ID

GHSA-fwcm-636p-68r5

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.