CVE-2017-5189: private SSL key embedded in JAR file in iManager
First published: Fri Mar 02 2018(Updated: )
NetIQ iManager before 3.0.3 delivered a SSL private key in a Java application (JAR file) for authentication to Sentinel, allowing attackers to extract and establish their own connections to the Sentinel appliance.
Credit: meissner@suse.de
| Affected Software | Affected Version | How to fix |
|---|---|---|
| NetIQ iManager | =2.7 | |
| NetIQ iManager | =2.7.1 | |
| NetIQ iManager | =2.7.2 | |
| NetIQ iManager | =2.7.3 | |
| NetIQ iManager | =2.7.4 | |
| NetIQ iManager | =2.7.5 | |
| NetIQ iManager | =2.7.6 | |
| NetIQ iManager | =2.7.7-p10 | |
| NetIQ iManager | =2.7.7-p11 | |
| NetIQ iManager | =2.7.7-p4 | |
| NetIQ iManager | =2.7.7-p5 | |
| NetIQ iManager | =2.7.7-p6 | |
| NetIQ iManager | =2.7.7-p7 | |
| NetIQ iManager | =2.7.7-p8 | |
| NetIQ iManager | =2.7.7-p9 | |
| NetIQ iManager | =2.7.7.10-hf1 | |
| NetIQ iManager | =2.7.7.10-hf2 | |
| NetIQ iManager | =3.0 | |
| NetIQ iManager | =3.0-sp1 | |
| NetIQ iManager | =3.0-sp2 | |
| NetIQ iManager | =3.0-sp3 | |
| NetIQ iManager | =3.0-sp4 | |
| NetIQ iManager | =3.0.2-p1 | |
| NetIQ iManager | =3.0.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-5189?
CVE-2017-5189 has a high severity rating due to its potential to expose SSL private keys, leading to unauthorized access to the Sentinel appliance.
How do I fix CVE-2017-5189?
To fix CVE-2017-5189, upgrade the affected NetIQ iManager version to 3.0.3 or later.
What software is affected by CVE-2017-5189?
CVE-2017-5189 affects various versions of NetIQ iManager, specifically versions 2.7, 2.7.x, and 3.0 before 3.0.3.
Can CVE-2017-5189 lead to data breaches?
Yes, CVE-2017-5189 can lead to data breaches as attackers can extract SSL private keys and establish unauthorized connections.
Is there a workaround for CVE-2017-5189?
Currently, the recommended solution for CVE-2017-5189 is to apply the appropriate software upgrade rather than relying on a temporary workaround.
- collector/nvd-index
- agent/weakness
- agent/references
- agent/type
- agent/softwarecombine
- agent/title
- agent/severity
- agent/author
- agent/description
- agent/tags
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- vendor/netiq
- canonical/netiq imanager
- version/netiq imanager/2.7
- version/netiq imanager/2.7.1
- version/netiq imanager/2.7.2
- version/netiq imanager/2.7.3
- version/netiq imanager/2.7.4
- version/netiq imanager/2.7.5
- version/netiq imanager/2.7.6
- version/netiq imanager/2.7.7-p10
- version/netiq imanager/2.7.7-p11
- version/netiq imanager/2.7.7-p4
- version/netiq imanager/2.7.7-p5
- version/netiq imanager/2.7.7-p6
- version/netiq imanager/2.7.7-p7
- version/netiq imanager/2.7.7-p8
- version/netiq imanager/2.7.7-p9
- version/netiq imanager/2.7.7.10-hf1
- version/netiq imanager/2.7.7.10-hf2
- version/netiq imanager/3.0
- version/netiq imanager/3.0-sp1
- version/netiq imanager/3.0-sp2
- version/netiq imanager/3.0-sp3
- version/netiq imanager/3.0-sp4
- version/netiq imanager/3.0.2-p1
- version/netiq imanager/3.0.3