{"answers":{"affected":"2 open source packages ship an affected version, including activestorage. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16477 in the wild and no public exploit code.","fix":"Upgrade activestorage to 5.2.1.1 or later.","what":"CVE-2018-16477 is a medium-severity cross-site scripting vulnerability in Rubyonrails Rails, published on 30 Nov 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-16477 and fix it if it is affected.\n\nWhat it is: CVE-2018-16477 is a medium-severity cross-site scripting vulnerability in Rubyonrails Rails, published on 30 Nov 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-16477 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- activestorage (RubyGems): affected from 5.2.0; fixed in 5.2.1.1\n- activestorage (RubyGems): affected from 5.2.0; fixed in 5.2.1.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-16477/ (Markdown: https://insights.sbomify.com/CVE-2018-16477/index.md)","id":"CVE-2018-16477","markdown":"https://insights.sbomify.com/CVE-2018-16477/index.md","name":"CVE-2018-16477","record":{"aliases":["DEBIAN-CVE-2018-16477","GHSA-7rr7-rcjw-56vj"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby on Rails","requires_auth":"none","summary":"Attackers can execute inline HTML via Active Storage bypass, potentially accessing private signed URLs and causing XSS.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"rails","vendor":"rubyonrails"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"A bypass vulnerability in Active Storage \u003e= 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.","ecosystems":["RubyGems"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Exposure of Sensitive Information to an Unauthorized Actor in activestorage","id":"CVE-2018-16477","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":"rubyonrails:rails","products":["rubyonrails:rails"],"type":"xss","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"Path Traversal in simplehttpserver","id":"CVE-2018-16478"},"packages":[{"ecosystem":"RubyGems","fixed":["5.2.1.1"],"introduced":["5.2.0"],"last_affected":[],"package":"activestorage","purl":null,"source":"GHSA-7rr7-rcjw-56vj"},{"ecosystem":"RubyGems","fixed":["5.2.1.1"],"introduced":["5.2.0"],"last_affected":[],"package":"activestorage","purl":"pkg:gem/activestorage","source":"GHSA-7rr7-rcjw-56vj"}],"prev":{"headline":"Improper Access Control in activejob","id":"CVE-2018-16476"},"products":["https://github.com/rails/rails"],"published":"2018-11-30","related":[{"cvss_score":10,"headline":"Active Record contains deserialization of arbitrary YAML","id":"CVE-2013-0277","kev_date_added":null,"published":"2013-02-13"},{"cvss_score":8.1,"headline":"SQL injection in n/a","id":"CVE-2017-17916","kev_date_added":null,"published":"2017-12-29"},{"cvss_score":8.1,"headline":"SQL injection in n/a","id":"CVE-2017-17917","kev_date_added":null,"published":"2017-12-29"},{"cvss_score":8,"headline":"Rails Active Storage has possible Path Traversal in DiskService","id":"CVE-2026-33195","kev_date_added":null,"published":"2026-03-23"},{"cvss_score":7.5,"headline":"Rails possible ReDoS vulnerability in Accept header parsing in Action Dispatch","id":"CVE-2024-26142","kev_date_added":null,"published":"2024-02-27"},{"cvss_score":7.5,"headline":"ReDoS based DoS vulnerability in Action Dispatch","id":"CVE-2023-22792","kev_date_added":null,"published":"2023-02-09"},{"cvss_score":7.5,"headline":"Denial of Service in Action Dispatch","id":"CVE-2021-22902","kev_date_added":null,"published":"2021-06-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can execute inline HTML via Active Storage bypass, potentially accessing private signed URLs and causing XSS.","url":"https://insights.sbomify.com/CVE-2018-16477/"}