GHSA-7rr7-rcjw-56vj CVE-2018-16477
Exposure of Sensitive Information to an Unauthorized Actor in activestorage
- Severity
- 6.5 / 10
- Medium · CVSS 3.0
- Exploit chance (EPSS)
- 1.31%
- Chance of exploitation in the next 30 days. Higher than 70.66% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
5.2.1.1- Upgrade activestorage to this version or later
Description
A bypass vulnerability in Active Storage >= 5.2.0 for Google Cloud Storage and Disk services allow an attacker to modify the content-disposition and content-type parameters which can be used in with HTML files and have them executed inline. Additionally, if combined with other techniques such as cookie bombing and specially crafted AppCache manifests, an attacker can gain access to private signed URLs within a specific storage path.
Vulnerable apps are those using either GCS or the Disk service in production. Other storage services such as S3 or Azure aren't affected.
Affected versions
RubyGems
| Package | Vulnerable | Fixed in |
|---|---|---|
| activestorage | >= 5.2.0, < 5.2.1.1 |
5.2.1.1 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
activestorage RubyGems → 5.2.1.1
- bundler
bundle update activestorage # Gemfile: gem "activestorage", ">= 5.2.1.1"
Severity breakdown
CVSS 3.0 6.5
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Weakness
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-xr9x-r78c-5hrm Active Storage has possible arbitrary file read and remote code execution in Active Storage variant processing | Critical | Also affects activestorage |
| GHSA-p9fm-f462-ggrg Rails Active Storage has a possible DoS vulnerability in proxy mode via multi-range requests | Medium | Also affects activestorage |
| GHSA-73f9-jhhh-hr5m Rails Active Storage has possible glob injection in its DiskService | Critical | Also affects activestorage |
| GHSA-9xrj-h377-fr87 Rails Active Storage has possible Path Traversal in DiskService | Critical | Also affects activestorage |
| GHSA-r46p-8f7g-vvvg Rails Active Storage has a possible DoS vulnerability when in proxy mode via Range requests | High | Also affects activestorage |
| GHSA-qcfx-2mfw-w4cg Rails Active Storage has possible content type bypass via metadata in direct uploads | Medium | Also affects activestorage |
| GHSA-r4mg-4433-c7g3 Active Storage allowed transformation methods that were potentially unsafe | High | Also affects activestorage |
| GHSA-8h22-8cf7-hq6g Rails has possible Sensitive Session Information Leak in Active Storage | Medium | Also affects activestorage |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor