{"answers":{"affected":"2 open source packages ship an affected version, including paratrooper-pingdom. It affects 1 product.","exploited":"There is no known exploitation of CVE-2014-1233 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2014-1233 yet. Limit exposure of the affected software until one is available.","what":"CVE-2014-1233 is a low-severity vulnerability in n/a, published on 10 Jan 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-2014-1233 and fix it if it is affected.\n\nWhat it is: CVE-2014-1233 is a low-severity vulnerability in n/a, published on 10 Jan 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-2014-1233 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- paratrooper-pingdom (RubyGems): affected all versions up to 1.0.0; no fix listed\n- paratrooper-pingdom (RubyGems): affected all versions up to 1.0.0; 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-1233/ (Markdown: https://insights.sbomify.com/CVE-2014-1233/index.md)","id":"CVE-2014-1233","markdown":"https://insights.sbomify.com/CVE-2014-1233/index.md","name":"CVE-2014-1233","record":{"aliases":["GHSA-fqrr-rrwg-69pv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ruby gem","requires_auth":"none","summary":"Local attackers can expose Pingdom API credentials by inspecting curl process arguments in the paratrooper-pingdom Ruby gem.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"paratrooper-pingdom","vendor":"tobias_maier"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/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 paratrooper-pingdom gem 1.0.0 for Ruby allows local users to obtain the App-Key, username, and password values by listing the curl 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":"Local API Login Credentials Disclosure in paratrooper-pingdom","id":"CVE-2014-1233","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"information_disclosure","year":"2014"},"n_packages":2,"n_references":2,"next":{"headline":"Paratrooper-newrelic Exposes of Sensitive Information to an Unauthorized Actor","id":"CVE-2014-1234"},"packages":[{"ecosystem":"RubyGems","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"paratrooper-pingdom","purl":null,"source":"GHSA-fqrr-rrwg-69pv"},{"ecosystem":"RubyGems","fixed":[],"introduced":["0"],"last_affected":["1.0.0"],"package":"paratrooper-pingdom","purl":"pkg:gem/paratrooper-pingdom","source":"GHSA-fqrr-rrwg-69pv"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2014-1232"},"products":["n/a"],"published":"2014-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 expose Pingdom API credentials by inspecting curl process arguments in the paratrooper-pingdom Ruby gem.","url":"https://insights.sbomify.com/CVE-2014-1233/"}