{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2011-2686 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2011-2686 is a medium-severity vulnerability in Ruby-Lang Ruby, published on 5 Aug 2011. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2011-2686 and fix it if it is affected.\n\nWhat it is: CVE-2011-2686 is a medium-severity vulnerability in Ruby-Lang Ruby, published on 5 Aug 2011. 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-2011-2686 in the wild and no public exploit code.\n\nAffected product: Ruby-Lang Ruby. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2011-2686/ (Markdown: https://insights.sbomify.com/CVE-2011-2686/index.md)","id":"CVE-2011-2686","markdown":"https://insights.sbomify.com/CVE-2011-2686/index.md","name":"CVE-2011-2686","record":{"aliases":["GHSA-g8g6-3p4h-6388"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby programming language","requires_auth":"none","summary":"Attackers can predict random numbers in forked Ruby processes due to improper seed resetting, potentially compromising cryptographic operations.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"ruby","vendor":"ruby-lang"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"Ruby before 1.8.7-p352 does not reset the random seed upon forking, which makes it easier for context-dependent attackers to predict the values of random numbers by leveraging knowledge of the number sequence obtained in a different child process, a related issue to CVE-2003-0900.  NOTE: this issue exists because of a regression during Ruby 1.8.6 development.","ecosystems":[],"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":"Weak cryptography in n/a","id":"CVE-2011-2686","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ruby-lang:ruby","products":["ruby-lang:ruby"],"type":"weak_cryptography","year":"2011"},"n_packages":0,"n_references":13,"next":{"headline":"Drupal Access Control Bypass","id":"CVE-2011-2687"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2011-2685"},"products":["n/a"],"published":"2011-08-05","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2009-4124","kev_date_added":null,"published":"2009-12-11"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2022-28738","kev_date_added":null,"published":"2022-05-09"},{"cvss_score":9.8,"headline":"Weak cryptography in OpenSSL extension of Ruby (Git trunk)","id":"CVE-2011-4121","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2017-17790","kev_date_added":null,"published":"2017-12-20"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-11465","kev_date_added":null,"published":"2017-07-19"},{"cvss_score":9.8,"headline":"Memory corruption in Ruby","id":"CVE-2016-2336","kev_date_added":null,"published":"2017-01-06"},{"cvss_score":9.8,"headline":"Code injection in Ruby","id":"CVE-2016-2337","kev_date_added":null,"published":"2017-01-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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 predict random numbers in forked Ruby processes due to improper seed resetting, potentially compromising cryptographic operations.","url":"https://insights.sbomify.com/CVE-2011-2686/"}