What is the severity of CVE-2017-7434?

CVE-2017-7434 has been assigned a medium severity level due to the potential exposure of sensitive information in exception logfiles.

How do I fix CVE-2017-7434?

To mitigate CVE-2017-7434, upgrade to NetIQ Identity Manager version 4.6 or later.

What types of information are affected by CVE-2017-7434?

CVE-2017-7434 specifically affects the logging of passwords in exception logfiles when incorrect XML configurations are sent.

Is the JDBC driver of NetIQ Identity Manager secure after the fix for CVE-2017-7434?

Yes, after upgrading to a version beyond 4.6, the security issue related to logging passwords is resolved.

Who is impacted by CVE-2017-7434?

Any organization using versions of NetIQ Identity Manager prior to 4.6 could potentially be impacted by CVE-2017-7434.

Vulnerability/
CVE-2017-7434

critical

9.8

CWE

532

2/3/2018

9/10/2019

CVE-2017-7434

First published: Fri Mar 02 2018(Updated: )

In the JDBC driver of NetIQ Identity Manager before 4.6 sending out incorrect XML configurations could result in passwords being logged into exception logfiles.

Credit: meissner@suse.de

Affected Software	Affected Version	How to fix
NetIQ Identity Manager	<4.6

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-7434?
CVE-2017-7434 has been assigned a medium severity level due to the potential exposure of sensitive information in exception logfiles.
How do I fix CVE-2017-7434?
To mitigate CVE-2017-7434, upgrade to NetIQ Identity Manager version 4.6 or later.
What types of information are affected by CVE-2017-7434?
CVE-2017-7434 specifically affects the logging of passwords in exception logfiles when incorrect XML configurations are sent.
Is the JDBC driver of NetIQ Identity Manager secure after the fix for CVE-2017-7434?
Yes, after upgrading to a version beyond 4.6, the security issue related to logging passwords is resolved.
Who is impacted by CVE-2017-7434?
Any organization using versions of NetIQ Identity Manager prior to 4.6 could potentially be impacted by CVE-2017-7434.

collector/nvd-index
agent/author
agent/severity
agent/references
agent/weakness
agent/tags
agent/type
agent/description
agent/event
vendor/netiq
canonical/netiq identity manager

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2017-7434?
CVE-2017-7434 has been assigned a medium severity level due to the potential exposure of sensitive information in exception logfiles.
How do I fix CVE-2017-7434?
To mitigate CVE-2017-7434, upgrade to NetIQ Identity Manager version 4.6 or later.
What types of information are affected by CVE-2017-7434?
CVE-2017-7434 specifically affects the logging of passwords in exception logfiles when incorrect XML configurations are sent.
Is the JDBC driver of NetIQ Identity Manager secure after the fix for CVE-2017-7434?
Yes, after upgrading to a version beyond 4.6, the security issue related to logging passwords is resolved.
Who is impacted by CVE-2017-7434?
Any organization using versions of NetIQ Identity Manager prior to 4.6 could potentially be impacted by CVE-2017-7434.