dbcve.org
EdirectoryApplication · Microfocus

CVE-2017-7429

HIGH · 8.8 CVSS v3.0 Published 2018-03-02
Fix available
A fix is available. Upgrade to after 8.8.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 certificate upload in NetIQ eDirectory PKI plugin before 8.8.8 Patch 10 Hotfix 1 could be abused to upload JSP code which could be used by authenticated attackers to execute JSP applets on the iManager server.

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

This is an authenticated file upload vulnerability in NetIQ eDirectory's PKI plugin certificate upload function. An authenticated attacker can upload JSP code disguised as a certificate, which can then be executed on the iManager server, leading to remote code execution.

MitigationApply vendor patch 8.8.8 Patch 10 Hotfix 1 or later to remediate. Additionally, restrict administrative access to the PKI plugin and iManager to trusted personnel only.

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
EdirectoryApplication
Affected:<= 8.8.8
EdirectoryApplication
Affected:= 8.8.8

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

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Identify eDirectory installation and version
    Check the eDirectory version by examining the ndsd daemon version or checking the installed RPM/Distribution package. Common paths: /opt/novell/eDirectory/bin/ndsd --version or rpm -qi eDirectory-ndsd. Also check /etc/novell-release or /etc/redhat-release for version info.
    Affected if The installed eDirectory version is 8.8.8 or lower (any version <= 8.8.8)
  2. Verify iManager web interface is enabled
    Check if the Tomcat-based iManager web application is running. Look for process: ps aux | grep -i tomcat or check netstat -tlnp for port 8080 or 8443 (default iManager ports). Also verify the iManager webapps directory exists: /var/opt/novell/tomcat9/webapps/ or /opt/novell/tomcat/webapps/.
    Affected if iManager is running and accessible on the network, providing a web interface for authentication
  3. Confirm PKI plugin is installed and enabled
    Check for the PKI plugin in the iManager plugins directory: typically found in /var/opt/novell/tomcat9/webapps/nps/WEB-INF/plugins/ or /opt/novell/tomcat/webapps/nps/WEB-INF/plugins/. Look for pki or certificate-related plugin folders. Also check the iManager configuration file for PKI module loading.
    Affected if The PKI plugin is installed and loaded in iManager, allowing certificate upload functionality
  4. Determine authentication accessibility to iManager
    Review LDAP authentication settings in eDirectory: check dhost.conf or nds.conf for authentication parameters. Verify if the iManager administrative accounts are accessible via LDAP on port 389 or 636. Determine if remote LDAP authentication is permitted and whether the PKI plugin requires administrative privileges.
    Affected if An attacker can obtain valid credentials to authenticate to iManager for certificate upload operations

Your environment is affected if eDirectory version is 8.8.8 or lower AND iManager with the PKI plugin is accessible to an authenticated user who can upload certificates.

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 a release after 8.8.8
Interim mitigation

Apply vendor patch 8.8.8 Patch 10 Hotfix 1 or later to remediate. Additionally, restrict administrative access to the PKI plugin and iManager to trusted personnel only.

Fix this in Edirectory Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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