dbcve.org
Identity ManagerApplication · Netiq

CVE-2017-7427

MEDIUM · 6.1 CVSS v3.0 Published 2018-03-05
Fix available
A fix is available. Upgrade to 4.6.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Multiple cross site scripting attacks were found in the Identity Manager Plug-in, hosted on iManager 2.7.7.7, before Identity Manager 4.6.1. In certain scenarios it was possible to execute arbitrary JavaScript code in the context of vulnerable application, via user.Context in the Object Selector, via vdtData in the Version discovery and via nextFrame in the Object Inspector and via Host GUID in the System details plugins.

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

Multiple stored cross-site scripting vulnerabilities exist in the Identity Manager Plug-in for iManager, affecting versions prior to 4.6.1 (including 2.7.7.7). Attackers can inject arbitrary JavaScript code through four distinct vectors: user.Context parameter in the Object Selector, vdtData in Version discovery, nextFrame in Object Inspector, and Host GUID in System details plugins. These vulnerabilities allow execution of malicious scripts in the context of the vulnerable application.

MitigationUpgrade Identity Manager to version 4.6.1 or later. Until patching is feasible, implement input validation and output encoding on all user-supplied parameters in the affected plug-ins, particularly the four identified vectors.

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:>= 2.7.7.7, < 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Check Identity Manager version
    Locate the installed version of NetIQ Identity Manager or the Identity Manager Plug-in for iManager. This is typically found in the plugin's about section, the iManager console, or the installed packages list.
    Affected if The installed version is 2.7.7.7 or higher but lower than 4.6.1.
  2. Verify Object Selector plugin is accessible
    Access the iManager interface and navigate to the Identity Manager section where the Object Selector component is available. Confirm the user.Context parameter can be submitted.
    Affected if The Object Selector plugin is loaded and accepts user-supplied input through the user.Context parameter.
  3. Verify Version discovery component is accessible
    Locate the Version discovery feature within the Identity Manager plug-in for iManager.
    Affected if The Version discovery component is enabled and accepts vdtData input.
  4. Verify Object Inspector is accessible
    Access the Object Inspector feature within iManager.
    Affected if The Object Inspector plugin is available and the nextFrame parameter can be manipulated.
  5. Verify System details plugin is accessible
    Navigate to the System details section of the Identity Manager plug-in.
    Affected if The System details plugin is present and accepts Host GUID input.

The environment is affected if the installed Identity Manager or Identity Manager Plug-in for iManager version falls within the range 2.7.7.7 to 4.6.0 and any of the four vulnerable components (Object Selector, Version discovery, Object Inspector, or System details) are accessible to users.

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.

From vendor data
Upgrade available Upgrade to 4.6.1 or later
Fixed in 4.6.1
Interim mitigation

Upgrade Identity Manager to version 4.6.1 or later. Until patching is feasible, implement input validation and output encoding on all user-supplied parameters in the affected plug-ins, particularly the four identified vectors.

Fix this in Identity Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7427 — 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-7427 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