Enterprise VirtualizationApplication · Redhat
CVE-2017-2614
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWhen 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn ovirt-aaa-jdbc-tool versions before 1.1.3, the password update functionality in the rhvm database fails to properly validate the current password when that password is expired. This allows an attacker who has obtained privileges to change passwords on accounts with expired passwords to bypass authentication and gain unauthorized access to those accounts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise VirtualizationApplication
= 4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ovirt-aaa-jdbc-tool installationRun 'rpm -q ovirt-aaa-jdbc-tool' or check for the tool in /usr/bin/ directoryAffected if The package is installed and version is below 1.1.3
-
Determine installed version numberExecute 'rpm -q --queryformat "%{VERSION}\n" ovirt-aaa-jdbc-tool' to retrieve the exact versionAffected if Version returned is less than 1.1.3 (e.g., 1.1.2, 1.1.1, 1.0.x)
-
Confirm Red Hat Enterprise Virtualization environmentCheck if running 'rhvm' database is present via 'psql -l' or database connection statusAffected if RHEV/RHV 4.0 environment with rhvm database is in use
-
Check for expired password accountsQuery the database for user accounts with expired passwords using: SELECT username, password, password_expired FROM authz_external_groups; or check via ovirt-aaa-jdbc-tool user-show commandAffected if Any user accounts exist where password_expired status is set to true or 1
User is affected if ovirt-aaa-jdbc-tool version is below 1.1.3 AND the rhvm database is present with at least one account having an expired password that could be exploited via the password update functionality.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade ovirt-aaa-jdbc-tool to version 1.1.3 or later to obtain the patch for proper expired password validation.
Fix this in Enterprise Virtualization
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2614 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-2614 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data