{"answers":{"affected":"2 open source packages ship an affected version, including ffi. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000201 in the wild and no public exploit code.","fix":"Upgrade ffi to 1.9.24 or later.","what":"CVE-2018-1000201 is a high-severity path traversal vulnerability in n/a, published on 22 Jun 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-1000201 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000201 is a high-severity path traversal vulnerability in n/a, published on 22 Jun 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-1000201 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ffi (RubyGems): affected all versions; fixed in 1.9.24\n- ffi (RubyGems): affected all versions; fixed in 1.9.24\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-1000201/ (Markdown: https://insights.sbomify.com/CVE-2018-1000201/index.md)","id":"CVE-2018-1000201","markdown":"https://insights.sbomify.com/CVE-2018-1000201/index.md","name":"CVE-2018-1000201","record":{"aliases":["GHSA-2gw2-8q9w-cw8p"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ruby FFI library","requires_auth":"none","summary":"Attackers can hijack DLL loading on Windows by using a Symbol as a DLL name, potentially leading to arbitrary code execution.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ruby-ffi","vendor":"ruby-ffi_project"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"ruby-ffi version 1.9.23 and earlier has a DLL loading issue which can be hijacked on Windows OS, when a Symbol is used as DLL name instead of a String This vulnerability appears to have been fixed in v1.9.24 and later.","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":"Ruby-ffi has a DLL loading issue","id":"CVE-2018-1000201","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"path_traversal","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins Groovy Postbuild Plugin vulnerable to Cross-site Scripting","id":"CVE-2018-1000202"},"packages":[{"ecosystem":"RubyGems","fixed":["1.9.24"],"introduced":["0"],"last_affected":[],"package":"ffi","purl":null,"source":"GHSA-2gw2-8q9w-cw8p"},{"ecosystem":"RubyGems","fixed":["1.9.24"],"introduced":["0"],"last_affected":[],"package":"ffi","purl":"pkg:gem/ffi","source":"GHSA-2gw2-8q9w-cw8p"}],"prev":{"headline":"Null dereference in n/a","id":"CVE-2018-1000200"},"products":["n/a"],"published":"2018-06-22","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 hijack DLL loading on Windows by using a Symbol as a DLL name, potentially leading to arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2018-1000201/"}