CVE-2009-0192
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 · uneditedOff-by-one error in the iMonitor component in Novell eDirectory 8.8 SP3, 8.8 SP3 FTF3, and possibly other versions allows remote attackers to execute arbitrary code via an HTTP request with a crafted Accept-Language header, which triggers a stack-based buffer overflow.
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 confidenceAn off-by-one error in the iMonitor component of Novell eDirectory allows remote attackers to cause a stack-based buffer overflow via a specially crafted Accept-Language HTTP header, potentially enabling arbitrary code execution.
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= 8.8CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify eDirectory versionCheck the installed Novell eDirectory version. On Windows, check the 'novell-eDirectory' or 'NDS' version in Add/Remove Programs, or run 'ndsstat' or 'ndsconfig' commands. On Linux/Unix, check using the package manager or run '/etc/init.d/ndsd version' or similar. Compare against the affected version: 8.8Affected if The installed version is exactly 8.8 (any subversion) or falls within the 8.8.x range
-
Confirm iMonitor component is installedVerify the iMonitor component is present on the system. Check for the iMonitor installation directory (typically under the eDirectory installation path, often named 'imanager' or 'imonitor'). Look for iMonitor executables or DLLs related to HTTP monitoring.Affected if iMonitor is installed and present on the system
-
Check if iMonitor HTTP interface is enabledLocate the iMonitor configuration file (commonly ndsimon.conf or similar configuration in the eDirectory config directory). Verify whether the HTTP listener/service for iMonitor is enabled. Also check if port 8088 or port 8008 (typical iMonitor ports) are open and listening.Affected if The iMonitor HTTP interface is enabled and listening on a network port, making it reachable via HTTP requests
-
Determine network exposure of iMonitorCheck which network interfaces and IP addresses the iMonitor HTTP service is bound to. Verify if it listens on all interfaces (0.0.0.0) or only localhost. Use 'netstat -an | grep -E "8088|8008"' or similar commands to identify listening ports and their binding addresses.Affected if iMonitor is bound to a publicly accessible IP address or is reachable from network segments beyond the local host, making the Accept-Language header exploitable via remote network access
A system is affected if it runs eDirectory version 8.8 with the iMonitor component installed, and the iMonitor HTTP interface is enabled and network-accessible, allowing remote attackers to send specially crafted Accept-Language headers.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the relevant Novell patch or upgrade to a patched version of eDirectory. If patching is not immediately possible, consider restricting access to the iMonitor HTTP interface via network segmentation or firewall rules.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-0192 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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