{"answers":{"affected":"2 open source packages ship an affected version, including bio-basespace-sdk. It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-7111 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-7111 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-7111 is a medium-severity vulnerability in n/a, published on 29 Apr 2014. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-7111 and fix it if it is affected.\n\nWhat it is: CVE-2013-7111 is a medium-severity vulnerability in n/a, published on 29 Apr 2014. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2013-7111 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- bio-basespace-sdk (RubyGems): affected all versions up to 0.1.7; no fix listed\n- bio-basespace-sdk (RubyGems): affected all versions up to 0.1.7; no fix listed\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-2013-7111/ (Markdown: https://insights.sbomify.com/CVE-2013-7111/index.md)","id":"CVE-2013-7111","markdown":"https://insights.sbomify.com/CVE-2013-7111/index.md","name":"CVE-2013-7111","record":{"aliases":["GHSA-xwr3-fmgj-mmfr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ruby SDK library","requires_auth":"none","summary":"Attackers can obtain sensitive API keys by listing processes, exposing credentials in the BaseSpace Ruby SDK.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"basespace_ruby_sdk","vendor":"basespace_ruby_sdk_project"}],"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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The put_call function in the API client (api/api_client.rb) in the BaseSpace Ruby SDK (aka bio-basespace-sdk) gem 0.1.7 for Ruby uses the API_KEY on the command line, which allows remote attackers to obtain sensitive information by listing the processes.","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":false,"headline":"Exposure of Sensitive Information in bio-basespace-sdk","id":"CVE-2013-7111","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"information_disclosure","year":"2013"},"n_packages":2,"n_references":3,"next":{"headline":"Denial of service in n/a","id":"CVE-2013-7112"},"packages":[{"ecosystem":"RubyGems","fixed":[],"introduced":["0"],"last_affected":["0.1.7"],"package":"bio-basespace-sdk","purl":null,"source":"GHSA-xwr3-fmgj-mmfr"},{"ecosystem":"RubyGems","fixed":[],"introduced":["0"],"last_affected":["0.1.7"],"package":"bio-basespace-sdk","purl":"pkg:gem/bio-basespace-sdk","source":"GHSA-xwr3-fmgj-mmfr"}],"prev":{"headline":"Transifex command-line client has improper certificate validation","id":"CVE-2013-7110"},"products":["n/a"],"published":"2014-04-29","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-06","vendors":["n/a"]},"summary":"Attackers can obtain sensitive API keys by listing processes, exposing credentials in the BaseSpace Ruby SDK.","url":"https://insights.sbomify.com/CVE-2013-7111/"}