{"answers":{"affected":"2 open source packages ship an affected version, including kajam. It affects 1 product.","exploited":"There is no known exploitation of CVE-2014-4999 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-4999 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-4999 is a high-severity vulnerability in n/a, published on 10 Jan 2018. 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-2014-4999 and fix it if it is affected.\n\nWhat it is: CVE-2014-4999 is a high-severity vulnerability in n/a, published on 10 Jan 2018. 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-2014-4999 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- kajam (RubyGems): affected all versions up to 1.0.3.rc2; no fix listed\n- kajam (RubyGems): affected all versions up to 1.0.3.rc2; 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-2014-4999/ (Markdown: https://insights.sbomify.com/CVE-2014-4999/index.md)","id":"CVE-2014-4999","markdown":"https://insights.sbomify.com/CVE-2014-4999/index.md","name":"CVE-2014-4999","record":{"aliases":["GHSA-4ph7-5c44-pppv"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ruby gem","requires_auth":"low_privilege","summary":"Local attackers can read MySQL passwords from process listings because the kajam gem exposes them in command-line arguments.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"kajam","vendor":"kajam_project"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"vendor/plugins/dataset/lib/dataset/database/mysql.rb in the kajam gem 1.0.3.rc2 for Ruby places the mysql user password on the (1) mysqldump command line in the capture function and (2) mysql command line in the restore function, which allows local users to obtain sensitive information by listing the process.","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":"kajam allows local users to obtain sensitive information by listing the process","id":"CVE-2014-4999","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"information_disclosure","year":"2014"},"n_packages":2,"n_references":3,"next":{"headline":"lawn-login exposes database password to unauthorized users","id":"CVE-2014-5000"},"packages":[{"ecosystem":"RubyGems","fixed":[],"introduced":["0"],"last_affected":["1.0.3.rc2"],"package":"kajam","purl":null,"source":"GHSA-4ph7-5c44-pppv"},{"ecosystem":"RubyGems","fixed":[],"introduced":["0"],"last_affected":["1.0.3.rc2"],"package":"kajam","purl":"pkg:gem/kajam","source":"GHSA-4ph7-5c44-pppv"}],"prev":{"headline":"lean-ruport allows local users to obtain sensitive information by listing the process","id":"CVE-2014-4998"},"products":["n/a"],"published":"2018-01-10","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":"Local attackers can read MySQL passwords from process listings because the kajam gem exposes them in command-line arguments.","url":"https://insights.sbomify.com/CVE-2014-4999/"}