{"answers":{"affected":"2 open source packages ship an affected version, including safemode. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-3693 in the wild and no public exploit code.","fix":"Upgrade safemode to 1.2.4 or later.","what":"CVE-2016-3693 is a high-severity vulnerability in n/a, published on 20 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-3693 and fix it if it is affected.\n\nWhat it is: CVE-2016-3693 is a high-severity vulnerability in n/a, published on 20 May 2016. 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-2016-3693 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- safemode (RubyGems): affected all versions; fixed in 1.2.4\n- safemode (RubyGems): affected all versions; fixed in 1.2.4\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-2016-3693/ (Markdown: https://insights.sbomify.com/CVE-2016-3693/index.md)","id":"CVE-2016-3693","markdown":"https://insights.sbomify.com/CVE-2016-3693/index.md","name":"CVE-2016-3693","record":{"aliases":["GHSA-c92m-rrrc-q5wf"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Ruby Safemode gem","requires_auth":"none","summary":"Attackers can obtain sensitive information from Rails controllers via the inspect method in the Safemode gem when a delegate object is initialized.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"safemode","vendor":"safemode_project"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-264","name":null},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The Safemode gem before 1.2.4 for Ruby, when initialized with a delegate object that is a Rails controller, allows context-dependent attackers to obtain sensitive information via the inspect method.","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":"safemode gem allows context-dependent attackers to obtain sensitive information via the inspect method","id":"CVE-2016-3693","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":2,"n_references":7,"next":{"headline":"SQL injection in n/a","id":"CVE-2016-3694"},"packages":[{"ecosystem":"RubyGems","fixed":["1.2.4"],"introduced":["0"],"last_affected":[],"package":"safemode","purl":null,"source":"GHSA-c92m-rrrc-q5wf"},{"ecosystem":"RubyGems","fixed":["1.2.4"],"introduced":["0"],"last_affected":[],"package":"safemode","purl":"pkg:gem/safemode","source":"GHSA-c92m-rrrc-q5wf"}],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2016-3692"},"products":["n/a"],"published":"2016-05-20","related":[{"cvss_score":9.8,"headline":"Safemode Gem Has Incomplete List of Disallowed Inputs","id":"CVE-2017-7540","kev_date_added":null,"published":"2017-07-21"}],"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-06","vendors":["n/a"]},"summary":"Attackers can obtain sensitive information from Rails controllers via the inspect method in the Safemode gem when a delegate object is initialized.","url":"https://insights.sbomify.com/CVE-2016-3693/"}