{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-1072 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2018-1072 is a medium-severity vulnerability in [UNKNOWN] ovirt-engine-setup, published on 26 Jun 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-1072 and fix it if it is affected.\n\nWhat it is: CVE-2018-1072 is a medium-severity vulnerability in [UNKNOWN] ovirt-engine-setup, published on 26 Jun 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-1072 in the wild and no public exploit code.\n\nAffected product: [UNKNOWN] ovirt-engine-setup. 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-1072/ (Markdown: https://insights.sbomify.com/CVE-2018-1072/index.md)","id":"CVE-2018-1072","markdown":"https://insights.sbomify.com/CVE-2018-1072/index.md","name":"CVE-2018-1072","record":{"aliases":["GHSA-9fw7-mcq9-ghf3"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"oVirt Engine","requires_auth":"low_privilege","summary":"Attackers can obtain database credentials if provisioning logs are shared, as passwords were logged in cleartext during specific backup operations.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"ovirt","vendor":"ovirt"},{"product":"enterprise_virtualization_manager","vendor":"redhat"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"ovirt-engine before version ovirt 4.2.2 is vulnerable to an information exposure through log files. When engine-backup was run with one of the options \"--provision*db\", the database username and password were logged in cleartext. Sharing the provisioning log might inadvertently leak database passwords.","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":"Information disclosure in ovirt-engine-setup","id":"CVE-2018-1072","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in ovirt-engine","id":"CVE-2018-1073"},"packages":[],"prev":{"headline":"Memory corruption in zsh","id":"CVE-2018-1071"},"products":["ovirt-engine-setup"],"published":"2018-06-26","related":[{"cvss_score":7.7,"headline":"Information disclosure in ovirt-engine","id":"CVE-2018-1074","kev_date_added":null,"published":"2018-04-26"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2014-7851","kev_date_added":null,"published":"2017-10-16"},{"cvss_score":7.2,"headline":"Information disclosure in ovirt-engine","id":"CVE-2017-15113","kev_date_added":null,"published":"2018-07-27"},{"cvss_score":6.8,"headline":"Auth bypass in n/a","id":"CVE-2014-0152","kev_date_added":null,"published":"2014-09-08"},{"cvss_score":6.5,"headline":"Missing authorization in ovirt-engine","id":"CVE-2019-3879","kev_date_added":null,"published":"2019-03-25"},{"cvss_score":5.9,"headline":"Information disclosure in ovirt-engine-metrics","id":"CVE-2019-10194","kev_date_added":null,"published":"2019-07-11"},{"cvss_score":5.5,"headline":"Information disclosure in n/a","id":"CVE-2016-6341","kev_date_added":null,"published":"2017-04-20"}],"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-05","vendors":["[UNKNOWN]"]},"summary":"Attackers can obtain database credentials if provisioning logs are shared, as passwords were logged in cleartext during specific backup operations.","url":"https://insights.sbomify.com/CVE-2018-1072/"}