Menu

Star on GitHub · 3.2k

CVE-2018-1075

5.0 · MEDIUM

ovirt-engine up to version 4.2.3 is vulnerable to an unfiltered password when choosing manual db provisioning.

Published Jun 12, 2018CWE-532EPSS 0.35%

Overview

CVE-2018-1075 is a medium-severity vulnerability. It was published on June 12, 2018 and has a CVSS 3.0 base score of 5.0 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 5.0, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

ovirt-engine up to version 4.2.3 is vulnerable to an unfiltered password when choosing manual db provisioning. When engine-setup was run and one chooses to provision the database manually or connect to a remote database, the password input was logged in cleartext during the verification step. Sharing the provisioning log might inadvertently leak database passwords.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2018-1075?

CVE-2018-1075 is a medium-severity vulnerability. It was published on June 12, 2018 and has a CVSS 3.0 base score of 5.0 (MEDIUM).

How severe is CVE-2018-1075?

This vulnerability has a CVSS 3.0 base score of 5.0, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2018-1075?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2018-1075?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2018-1075 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2018

View all