dbcve.org
EdirectoryApplication · Novell

CVE-2008-0926

HIGH · 7.5 CVSS v2.0 Published 2008-03-28
Fix available
A fix is available. Upgrade to after 8.7.3.10 or later.
See remediation →
84/100
Remediation priority · High
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
The SOAP interface to the eMBox module in Novell eDirectory 8.7.3.9 and earlier, and 8.8.x before 8.8.2, relies on client-side authentication, which allows remote attackers to bypass authentication via requests for /SOAP URIs, and cause a denial of service (daemon shutdown) or read arbitrary files. NOTE: it was later reported that 8.7.3.10 (aka 8.7.3 SP10) is also affected.

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

The SOAP interface to the eMBox module in Novell eDirectory versions 8.7.3.9 and earlier, 8.7.3.10 (SP10), and 8.8.x before 8.8.2 incorrectly relies on client-side authentication rather than server-side validation. This allows remote unauthenticated attackers to send requests directly to /SOAP URIs to bypass authentication, read arbitrary files from the system, or cause a denial of service by shutting down the eDirectory daemon.

MitigationUpgrade to Novell eDirectory 8.8.2 or later. If upgrading is not immediately feasible, disable the SOAP/eMBox service if not required and restrict network access to the eDirectory SOAP port via firewall rules.

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.7.3.10= 8.5= 8.5.12a= 8.5.27= 8.6.2= 8.7= 8.7.1= 8.7.3= 8.7.3.8= 8.7.3.8_presp9= 8.7.3.9= 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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

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

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. Determine installed eDirectory version
    Run 'ndsd -v' or 'ndsconfig get' to retrieve the eDirectory version. On Windows, check the version via the Novell eDirectory installed programs in Control Panel, or query the registry key 'HKLM\SOFTWARE\Novell\eDirectory\version'. On Linux/Unix, check '/etc/dxcluster.ini' or run 'ndsmanage' to view version information.
    Affected if The installed version is any of: 8.5, 8.5.12a, 8.5.27, 8.6.2, 8.7, 8.7.1, 8.7.3, 8.7.3.8, 8.7.3.8_presp9, 8.7.3.9, 8.7.3.10, or any 8.8.x version before 8.8.2.
  2. Verify if SOAP/eMBox service is enabled
    Check if the eMBox (eDirectory Management Toolbox) SOAP interface is enabled in the eDirectory configuration. On Linux/Unix, examine '/etc/dxdircfg.xml' or the NDS configuration for eMBox settings. On Windows, check the eDirectory snap-ins in Novell iManager or the NDS registry entries under 'HKLM\SOFTWARE\Novell\eDirectory\eMBox'. Alternatively, run 'ndsmanage' and look for eMBox or SOAP service status.
    Affected if The SOAP/eMBox service is enabled and running.
  3. Confirm SOAP port is listening
    Check if the SOAP port (default 8028, or configured port) is open and listening. Run 'netstat -an | grep 8028' or 'ss -tlnp | grep 8028' on the eDirectory server. Verify the port is bound to a network interface accessible remotely.
    Affected if Port 8028 (or the configured SOAP port) is listening and bound to a reachable network address.
  4. Test SOAP endpoint accessibility
    Send an HTTP GET request to 'http://<server>:8028/SOAP' or 'http://<server>:8028/SOAP/eMBox' using curl or a browser from an external host. If authentication is bypassable, the endpoint will respond without requiring credentials.
    Affected if The /SOAP URI responds to unauthenticated requests or returns an error indicating the SOAP interface is exposed.

You are affected if your eDirectory version matches the vulnerable ranges AND the SOAP/eMBox service is enabled and network-accessible, allowing unauthenticated SOAP requests.

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.7.3.10
Interim mitigation

Upgrade to Novell eDirectory 8.8.2 or later. If upgrading is not immediately feasible, disable the SOAP/eMBox service if not required and restrict network access to the eDirectory SOAP port via firewall rules.

Fix this in Edirectory Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,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 $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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