{"answers":{"affected":"4 open source packages ship an affected version, including rack-protection. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000119 in the wild and no public exploit code.","fix":"Upgrade rack-protection to a fixed version for your release line: 1.5.5 or 2.0.0.","what":"CVE-2018-1000119 is a medium-severity vulnerability in n/a, published on 7 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1000119 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000119 is a medium-severity vulnerability in n/a, published on 7 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-1000119 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rack-protection (RubyGems): affected all versions; fixed in 1.5.5\n- rack-protection (RubyGems): affected all versions; fixed in 1.5.5\n- rack-protection (RubyGems): affected from 2.0.0.beta1; fixed in 2.0.0\n- rack-protection (RubyGems): affected from 2.0.0.beta1; fixed in 2.0.0\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-1000119/ (Markdown: https://insights.sbomify.com/CVE-2018-1000119/index.md)","id":"CVE-2018-1000119","markdown":"https://insights.sbomify.com/CVE-2018-1000119/index.md","name":"CVE-2018-1000119","record":{"aliases":["DSA-4247-1","GHSA-688c-3x49-6rqj","UBUNTU-CVE-2018-1000119"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby web framework","requires_auth":"none","summary":"Attackers can bypass CSRF protection in Sinatra applications via timing attacks on token checks, potentially enabling unauthorized actions.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"rack-protection","vendor":"sinatrarb"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"Sinatra rack-protection versions 1.5.4 and 2.0.0.rc3 and earlier contains a timing attack vulnerability in the CSRF token checking that can result in signatures can be exposed. This attack appear to be exploitable via network connectivity to the ruby application. This vulnerability appears to have been fixed in 1.5.5 and 2.0.0.","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":"rack-protection gem timing attack vulnerability when validating CSRF token","id":"CVE-2018-1000119","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":4,"n_references":4,"next":{"headline":"curl FTP path confusion leads to NIL byte out of bounds write","id":"CVE-2018-1000120"},"packages":[{"ecosystem":"RubyGems","fixed":["1.5.5"],"introduced":["0"],"last_affected":[],"package":"rack-protection","purl":null,"source":"GHSA-688c-3x49-6rqj"},{"ecosystem":"RubyGems","fixed":["1.5.5"],"introduced":["0"],"last_affected":[],"package":"rack-protection","purl":"pkg:gem/rack-protection","source":"GHSA-688c-3x49-6rqj"},{"ecosystem":"RubyGems","fixed":["2.0.0"],"introduced":["2.0.0.beta1"],"last_affected":[],"package":"rack-protection","purl":null,"source":"GHSA-688c-3x49-6rqj"},{"ecosystem":"RubyGems","fixed":["2.0.0"],"introduced":["2.0.0.beta1"],"last_affected":[],"package":"rack-protection","purl":"pkg:gem/rack-protection","source":"GHSA-688c-3x49-6rqj"}],"prev":{"headline":"Electron protocol handler browser vulnerable to Command Injection","id":"CVE-2018-1000118"},"products":["n/a"],"published":"2018-03-07","related":[],"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 bypass CSRF protection in Sinatra applications via timing attacks on token checks, potentially enabling unauthorized actions.","url":"https://insights.sbomify.com/CVE-2018-1000119/"}