CVE-2016-6341 json
oVirt Engine before 4.0.3 does not include DWH_DB_PASSWORD in the list of keys to hide in log files, which allows local users to obtain sen…
published 2017-04-20 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-7268
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
oVirt Engine before 4.0.3 does not include DWH_DB_PASSWORD in the list of keys to hide in log files, which allows local users to obtain sensitive password information by reading engine log files.
Patch / fix
- ovirt.org/release/4.0.3/ advisory
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-2016-6341 updated cvss 5.9
ovirt-engine: DWH_DB_PASSWORD is in cleartext in the log files
-
Red Hat Enterprise Virtualization 3 ovirt-engine Red Hat Virtualization 4 rhvm, ovirt-engine, ovirt-engine-setup, ovirt-engine-tools, ovirt-engine-backend, ovirt-engine-restapi, +14 moreaffected: no fix available
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.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
ovirt.org
/release/4.0.3/
patch, vendor-advisory
-
securityfocus.com
/bid/92665
vdb-entry, third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=1363816
issue-tracking
-
bugzilla.redhat.com
/show_bug.cgi?id=1369793
issue-tracking
Sources
- CVE List CVE-2016-6341
- NVD CVE-2016-6341
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.