Edirectory vulnerabilitiesRanked by how likely they are to be used.

Product44 versions
The short answer

Edirectory is made by Microfocus. We track 16 published vulnerabilities in it, across 44 versions. None of them is on the list of flaws known to be exploited today. If you run Edirectory, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Edirectory vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Edirectory's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Edirectory flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 59%

    Stack-based buffer overflow in the Novell NCP implementation in NetIQ eDirectory 8.8.7.x before 8.8.7.2 allows remote attackers to have an unspecified impact via unknown vectors.

    CVSS10.0Published25 Dec 2012
  2. 2.2%

    Unspecified vulnerability in NetIQ eDirectory 8.8.6.x before 8.8.6.7 and 8.8.7.x before 8.8.7.2 on Windows allows remote attackers to obtain an administrator cookie and bypass authorization checks via unknown vectors.

    CVSS6.4Published25 Dec 2012
  3. 1.9%

    dhost in NetIQ eDirectory 8.8.6.x before 8.8.6.7 and 8.8.7.x before 8.8.7.2 on Windows allows remote authenticated users to cause a denial of service (daemon crash) via crafted characters in an HTTP request.

    CVSS4.0Published25 Dec 2012
  4. 1.8%

    Cross-site scripting (XSS) vulnerability in NetIQ eDirectory 8.8.6.x before 8.8.6.7 and 8.8.7.x before 8.8.7.2 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

    CVSS4.3Published25 Dec 2012
  5. 1.4%

    Information leakage vulnerability in NetIQ eDirectory before 9.1.1 HF1 due to shared memory usage.

    CVSS7.5Published9 Aug 2018
  6. 1.2%

    NetIQ eDirectory before 9.0 SP4 did not enforce login restrictions when "ebaclient" was used, allowing unpermitted access to eDirectory services.

    CVSS9.8Published2 Mar 2018
  7. 0.8%

    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.

    CVSS8.8Published2 Mar 2018
  8. 0.8%

    Incorrect enforcement of authorization checks in eDirectory prior to 9.1 SP2

    CVSS7.5Published12 Dec 2018
  9. 0.6%

    Unvalidated redirect vulnerability in in NetIQ eDirectory before 9.1.1 HF1.

    CVSS6.1Published9 Aug 2018
  10. 0.6%

    Cross site scripting vulnerability in eDirectory prior to 9.1 SP2

    CVSS6.1Published12 Dec 2018
Precursor Intelligence

Running Edirectory? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 16 published vulnerabilities listed under the name Edirectory, across 44 versions.

None of Edirectory's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Edirectory. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.