Skip to content
Fencer Intel
medium 6.8

CVE-2017-2614 json

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 i…

published 8y ago modified 4mo ago also EUVD-2017-11775

cvss
6.8
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 20%
public exploits
0
none known

Summary

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.

Patch / fix

  • ovirt-engine-extension-aaa-jdbc rhev manager 4 1.1.3-1.el7ev

red hat advisories RHSA-2017:0257

Is CVE-2017-2614 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-2614 updated cvss 6.8

rhev-m-4: Fails to validate existing expired passwords when changing a password

  • Red Hat RHEV-M 4.0 ovirt-engine-extension-aaa-jdbc 1.1.3-1.el7ev
    fixed: vendor fix RHSA-2017:0257

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 6.8 CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
NVD 3.0 6.3 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:P/A:N

Affected products

  • Red Hat ovirt-engine-extension-aaa-jdbc

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-640 Weak Password Recovery Mechanism for Forgotten Password

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.