dbcve.org
Identity ManagerApplication · Netiq

CVE-2017-7426

CRITICAL · 9.1 CVSS v3.0 Published 2018-03-01
Fix available
A fix is available. Upgrade to 4.6.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The NetIQ Identity Manager Plugins before 4.6.1 contained various XML External XML Entity (XXE) handling flaws that could be used by attackers to leak information or cause denial of service attacks.

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 · high confidence

NetIQ Identity Manager Plugins before version 4.6.1 contain multiple XML External Entity (XXE) vulnerabilities. The application parses XML input without properly disabling external entity processing, allowing attackers to inject malicious XML that can read local files from the server or cause denial of service by exhausting server resources.

MitigationUpgrade NetIQ Identity Manager Plugins to version 4.6.1 or later. If immediate upgrading is not possible, disable external entity processing in the XML parser configuration and implement strict input validation for all XML data.

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
Identity ManagerApplication
Affected:< 4.6.1

CVSS 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify NetIQ Identity Manager Plugins is installed
    Locate the NetIQ Identity Manager Plugins installation directory or check system inventory for the product. Common locations include the NetIQ IDM directory structure or add-on/plugin folders.
    Affected if The product is not found on the system, then it is not affected. If found, proceed to version check.
  2. Determine the installed version of NetIQ Identity Manager Plugins
    Check the plugins version file, about dialog, or version information in the installation directory. Look for a version file, manifest, or product information file that lists the exact version number.
    Affected if The installed version cannot be determined - you cannot confirm if the vulnerability is present without a verifiable version number.
  3. Compare installed version against the affected range
    Compare the discovered version number to the affected range: any version before 4.6.1 is vulnerable. If the version is 4.6.1 or later, the issue has been patched.
    Affected if The version is less than 4.6.1 (for example, 4.5.x, 4.0.x, or any earlier release), indicating the vulnerable version is installed.
  4. Confirm XML processing functionality is in use
    Identify if the system processes XML input through NetIQ Identity Manager Plugins, such as configuration files, workflow definitions, or data import features that accept XML content.
    Affected if The system processes XML input through the Identity Manager Plugins - this is the attack surface for the XXE vulnerability. If no XML processing occurs, the practical risk is reduced though the vulnerability still exists in the code.

If NetIQ Identity Manager Plugins version is installed and the version is less than 4.6.1, the environment is affected by this XXE vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 4.6.1 or later
Fixed in 4.6.1
Interim mitigation

Upgrade NetIQ Identity Manager Plugins to version 4.6.1 or later. If immediate upgrading is not possible, disable external entity processing in the XML parser configuration and implement strict input validation for all XML data.

Recommended fix High confidence

4.6.1

  1. 1. Back up the current Identity Manager configuration and database before beginning any upgrade
  2. 2. Download Identity Manager version 4.6.1 or later from the official Micro Focus/Novell download portal
  3. 3. Review the official upgrade documentation for Identity Manager to understand prerequisites and installation procedures
  4. 4. Install or upgrade the Identity Manager Plugins to version 4.6.1 following the vendor's documented upgrade process
  5. 5. After upgrade, verify that the XML parser configurations disable external entity processing to confirm the XXE vulnerability is addressed
  6. 6. Test that Identity Manager functionality remains operational after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Identity Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7426 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-7426 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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