CVE-2016-6341: Infoleak

Published Aug 24, 2016
·
Updated

It was found that the value of property DWHDBPASSWORD can be found in the log files.

Product bug:

https://bugzilla.redhat.com/showbug.cgi?id=1363816

Other sources

oVirt Engine before 4.0.3 does not include DWHDBPASSWORD in the list of keys to hide in log files, which allows local users to obtain sensitive password information by reading engine log files.

MITRE

Affected Software

1 affected component
Ovirt oVirt<=4.0.2

Remediation

Event History

Aug 24, 2016
Data Sourced
via Red Hat·12:20 PM
DescriptionSeverityAffected Software
Apr 20, 2017
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2016-6341?

CVE-2016-6341 has a medium severity rating due to the exposure of sensitive database passwords in log files.

2

How do I fix CVE-2016-6341?

To fix CVE-2016-6341, upgrade to a version of oVirt that addresses the logging issue and prevents sensitive information from being logged.

3

Which versions of oVirt are affected by CVE-2016-6341?

CVE-2016-6341 affects oVirt versions up to and including 4.0.2.

4

What information is exposed in CVE-2016-6341?

CVE-2016-6341 exposes the DWH_DB_PASSWORD property in log files, which can lead to potential unauthorized access.

5

Is there a workaround for CVE-2016-6341?

As a workaround for CVE-2016-6341, you can manually delete sensitive information from the logs, but updating to a secure version is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203