{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000060 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2018-1000060 is a critical vulnerability in n/a, published on 9 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1000060 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000060 is a critical vulnerability in n/a, published on 9 Feb 2018. 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-2018-1000060 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2018-1000060/ (Markdown: https://insights.sbomify.com/CVE-2018-1000060/index.md)","id":"CVE-2018-1000060","markdown":"https://insights.sbomify.com/CVE-2018-1000060/index.md","name":"CVE-2018-1000060","record":{"aliases":["RHSA-2018:0616","RHSA-2018:1112","RHSA-2018:1606"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Sensu monitoring server","requires_auth":"none","summary":"Attackers with log access can view sensitive configuration data like passwords due to improper redaction in Sensu Core.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sensu_core","vendor":"sensu"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Sensu, Inc. Sensu Core version Before 1.2.0 \u0026 before commit 46ff10023e8cbf1b6978838f47c51b20b98fe30b contains a CWE-522 vulnerability in Sensu::Utilities.redact_sensitive() that can result in sensitive configuration data (e.g. passwords) may be logged in clear-text. This attack appear to be exploitable via victims with configuration matching a specific pattern will observe sensitive data outputted in their service log files. This vulnerability appears to have been fixed in 1.2.1 and later, after commit 46ff10023e8cbf1b6978838f47c51b20b98fe30b.","ecosystems":["Red Hat:openstack-optools:10::el7","Red Hat:openstack-optools:11::el7","Red Hat:openstack-optools:12::el7"],"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":"Information disclosure in n/a","id":"CVE-2018-1000060","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":5,"n_references":5,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2018-1000061"},"packages":[{"ecosystem":"Red Hat:openstack-optools:10::el7","fixed":["0:0.23.2-4.el7ost"],"introduced":["0"],"last_affected":[],"package":"sensu","purl":"pkg:rpm/redhat/sensu","source":"RHSA-2018:1606"},{"ecosystem":"Red Hat:openstack-optools:11::el7","fixed":["0:0.27.0-4.el7ost"],"introduced":["0"],"last_affected":[],"package":"sensu","purl":"pkg:rpm/redhat/sensu","source":"RHSA-2018:1112"},{"ecosystem":"Red Hat:openstack-optools:11::el7","fixed":["0:0.27.0-4.el7ost"],"introduced":["0"],"last_affected":[],"package":"sensu-common","purl":"pkg:rpm/redhat/sensu-common","source":"RHSA-2018:1112"},{"ecosystem":"Red Hat:openstack-optools:12::el7","fixed":["0:0.27.0-4.el7ost"],"introduced":["0"],"last_affected":[],"package":"sensu","purl":"pkg:rpm/redhat/sensu","source":"RHSA-2018:0616"},{"ecosystem":"Red Hat:openstack-optools:12::el7","fixed":["0:0.27.0-4.el7ost"],"introduced":["0"],"last_affected":[],"package":"sensu-common","purl":"pkg:rpm/redhat/sensu-common","source":"RHSA-2018:0616"}],"prev":{"headline":"Deserialization in n/a","id":"CVE-2018-1000059"},"products":["n/a"],"published":"2018-02-09","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-1000209","kev_date_added":null,"published":"2018-07-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"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-05","vendors":["n/a"]},"summary":"Attackers with log access can view sensitive configuration data like passwords due to improper redaction in Sensu Core.","url":"https://insights.sbomify.com/CVE-2018-1000060/"}