dbcve.org
EdirectoryApplication · Microfocus

CVE-2012-0432

HIGH · 10.0 CVSS v2.0 Published 2012-12-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
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.

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

Stack-based buffer overflow in the Novell NCP (Novell Core Protocol) implementation in NetIQ eDirectory versions 8.8.7.x before 8.8.7.2. The vulnerability allows remote attackers to execute arbitrary code via unspecified vectors by overflowing a stack-based buffer in the NCP service.

MitigationUpgrade NetIQ eDirectory to version 8.8.7.2 or later to address the stack-based buffer overflow vulnerability. If immediate patching is not possible, consider network segmentation to limit exposure of the eDirectory service.

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.7.0= 8.8.7.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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 if eDirectory is installed
    On Windows, check the installed programs list or registry for 'eDirectory' or 'NetIQ eDirectory'. On Linux/Unix, run 'rpm -qa | grep -i edirectory' or check /opt/novell for eDirectory installation directories.
    Affected if eDirectory software is found on the system
  2. Determine the eDirectory version
    On Windows, check the version property of the eDirectory service executable or check the Windows registry under HKLM\SOFTWARE\Novell\eDirectory. On Linux/Unix, run 'ndsconfig --version' or check the version file in the eDirectory installation directory (typically /opt/novell/eDirectory/).
    Affected if The installed version is 8.8.7.0 or 8.8.7.1 (or any 8.8.7.x version prior to 8.8.7.2)
  3. Verify the NCP service is enabled and running
    On Windows, open Services and look for 'NetIQ eDirectory Service - NCP Server' or check if ncp server is running. On Linux/Unix, check if the ncp.nlm or ncpd daemon is running (ps aux | grep ncp).
    Affected if The NCP (Novell Core Protocol) service is active on the server
  4. Check if NCP port is exposed to the network
    Run 'netstat -an | grep 524' or 'ss -tlnp | grep 524' to verify if TCP port 524 (NCP) is listening on interfaces accessible from untrusted networks. Use a network scanner to confirm external accessibility if needed.
    Affected if Port 524 is listening on a network interface accessible to untrusted users or networks

The environment is affected if eDirectory versions 8.8.7.0 or 8.8.7.1 are installed with the NCP service enabled and exposed to the network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade NetIQ eDirectory to version 8.8.7.2 or later to address the stack-based buffer overflow vulnerability. If immediate patching is not possible, consider network segmentation to limit exposure of the eDirectory service.

Recommended fix High confidence

eDirectory 8.8.7.2

  1. 1. Verify the current eDirectory version by checking the installed software or using the iMonitor utility.
  2. 2. Confirm the installation is either 8.8.7.0 or 8.8.7.1, which are affected by CVE-2012-0432.
  3. 3. Plan the upgrade during a maintenance window to minimize business impact.
  4. 4. Download NetIQ eDirectory 8.8.7.2 or later from the Novell/NetIQ download portal.
  5. 5. Review the upgrade documentation and release notes for eDirectory 8.8.7.2.
  6. 6. Perform a full backup of the eDirectory database and configuration files before upgrading.
  7. 7. Run the eDirectory installer to upgrade to version 8.8.7.2 or later.
  8. 8. Verify the upgrade was successful by checking the version in iMonitor or by running the appropriate version check command.
Caveat Review release notes for any known issues or configuration changes required when upgrading from 8.8.7.x to 8.8.7.2

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

Fix this in Edirectory Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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