Menu

Star on GitHub · 3.2k

CVE-2017-2614

6.8 · MEDIUM

When updating a password in the rhvm database the ovirt-aaa-jdbc-tool tools before 1.1.3 fail to correctly check for the current password if it is expired.

Published Jul 27, 2018CWE-20EPSS 0.28%

Overview

CVE-2017-2614 is a medium-severity vulnerability. It was published on July 27, 2018 and has a CVSS 3.0 base score of 6.8 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 6.8, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

When updating a password in the rhvm database the ovirt-aaa-jdbc-tool tools before 1.1.3 fail to correctly check for the current password if it is expired. This would allow access to an attacker with access to change the password on accounts with expired passwords, gaining access to those accounts.

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-2017-2614?

CVE-2017-2614 is a medium-severity vulnerability. It was published on July 27, 2018 and has a CVSS 3.0 base score of 6.8 (MEDIUM).

How severe is CVE-2017-2614?

This vulnerability has a CVSS 3.0 base score of 6.8, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2017-2614?

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-2017-2614?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2017-2614 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 2017

View all