CVE-2018-16477
published 2018-11-30CVE-2018-16477: 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…
PriorityP433medium6.5CVSS 3.0
AVNACLPRNUIRSUCNIHAN
EPSS
1.31%
67.5th percentile
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. This vulnerability has been fixed in version 5.2.1.1.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | rails | < rails 2:5.2.2+dfsg-1 (bookworm) | rails 2:5.2.2+dfsg-1 (bookworm) |
| https | github.com_rails_rails | — | — |
| rails | activestorage | >= 5.2.0 < 5.2.1.1 | 5.2.1.1 |
| rubyonrails | rails | >= 0 < 2:5.2.2+dfsg-1 | 2:5.2.2+dfsg-1 |
| rubyonrails | rails | >= 0 < 2:5.2.2+dfsg-1 | 2:5.2.2+dfsg-1 |
| rubyonrails | rails | >= 0 < 2:5.2.2+dfsg-1 | 2:5.2.2+dfsg-1 |
| rubyonrails | rails | >= 0 < 2:5.2.2+dfsg-1 | 2:5.2.2+dfsg-1 |
| rubyonrails | rails | >= 5.2.0 < 5.2.1.1 | 5.2.1.1 |
CVSS provenance
nvdv3.06.5MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:P/A:N
osv6.5MEDIUM
vendor_debian6.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Debian
CVE-2018-16477: rails - A bypass vulnerability in Active Storage >= 5.2.0 for Google Cloud Storage and D...
vendor_debian·2018·CVSS 6.5
CVE-2018-16477 [MEDIUM] CVE-2018-16477: rails - A bypass vulnerability in Active Storage >= 5.2.0 for Google Cloud Storage and D...
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. This vulnerability has been fixed in version 5.2.1.1.
Scope: local
bookworm: resolved (fixed in 2:5.2.2+dfsg-1)
bullseye: resolved (fixed in 2:5.2.2+dfsg-1)
forky: resolved (fixed in 2:5.2.2+dfsg-1)
sid: resolved (fixed in 2:5.2.2+dfsg-1)
trixie: resolved (fixed in 2:5.2.2+dfsg-1)
GHSA
Exposure of Sensitive Information to an Unauthorized Actor in activestorage
ghsa·2018-12-05
CVE-2018-16477 [MEDIUM] CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in activestorage
Exposure of Sensitive Information to an Unauthorized Actor in activestorage
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.
OSV
Exposure of Sensitive Information to an Unauthorized Actor in activestorage
osv·2018-12-05
CVE-2018-16477 [MEDIUM] Exposure of Sensitive Information to an Unauthorized Actor in activestorage
Exposure of Sensitive Information to an Unauthorized Actor in activestorage
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.
OSV
CVE-2018-16477: A bypass vulnerability in Active Storage >= 5
osv·2018-11-30·CVSS 6.5
CVE-2018-16477 [MEDIUM] CVE-2018-16477: A bypass vulnerability in Active Storage >= 5
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. This vulnerability has been fixed in version 5.2.1.1.
No detection rules found.
No public exploits indexed.
HackerOne
ActiveStorage service's signed URLs can be hijacked via AppCache+Cookie stuffing trick when using GCS or DiskService
hackerone·2018-12-27·CVSS 7.4
[HIGH] ActiveStorage service's signed URLs can be hijacked via AppCache+Cookie stuffing trick when using GCS or DiskService
ActiveStorage service's signed URLs can be hijacked via AppCache+Cookie stuffing trick when using GCS or DiskService
`ActiveStorage` tries to force `content-disposition: attachment` for [a list of content-types](https://github.com/rails/rails/blob/2a470d73a75ebf8cd7975e469bd82586d9234442/activestorage/lib/active_storage/engine.rb#L33-L42), including `text/html`. However, `response-content-type` and `response-content-disposition` in GCS and DiskService's URLs aren't signed, which means an attacker can modify them at will. This is not the case for Azure or S3.
This can be exploited using `AppCache` and cookie bombing as follows:
1. Upload the following file as `ActiveStorage::Blob`
File: fallback.html
```
alert('Your request to the page '+location.href+' is hijacked!');
```
Grab the se
Bugzilla
CVE-2018-16477 rubygem-activestorage: bypass vulnerability in Google Cloud Storage and Disk services
bugzilla·2018-12-13·CVSS 6.5
CVE-2018-16477 [MEDIUM] CVE-2018-16477 rubygem-activestorage: bypass vulnerability in Google Cloud Storage and Disk services
CVE-2018-16477 rubygem-activestorage: bypass vulnerability in Google Cloud Storage and Disk services
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.
References:
https://groups.google.com/d/msg/rubyonrails-security/3KQRnXDIuLg/mByx5KkqBAAJ
https://weblog.rubyonrails.org/2018/11/27/Rails-4-2-5-0-5-1-5-2-have-been-released/
Discussion:
Created rubygem-activestorage tracking bugs for this issue:
Affect
Bugzilla
CVE-2018-16477 rubygem-activestorage: bypass vulnerability in Google Cloud Storage and Disk services [fedora-all]
bugzilla·2018-12-13·CVSS 6.5
CVE-2018-16477 [MEDIUM] CVE-2018-16477 rubygem-activestorage: bypass vulnerability in Google Cloud Storage and Disk services [fedora-all]
CVE-2018-16477 rubygem-activestorage: bypass vulnerability in Google Cloud Storage and Disk services [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue
https://groups.google.com/d/msg/rubyonrails-security/3KQRnXDIuLg/mByx5KkqBAAJhttps://weblog.rubyonrails.org/2018/11/27/Rails-4-2-5-0-5-1-5-2-have-been-released/https://groups.google.com/d/msg/rubyonrails-security/3KQRnXDIuLg/mByx5KkqBAAJhttps://weblog.rubyonrails.org/2018/11/27/Rails-4-2-5-0-5-1-5-2-have-been-released/
2018-11-30
Published