CVE-2021-22503
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 · uneditedPossible Improper Neutralization of Input During Web Page Generation Vulnerability in eDirectory has been discovered in OpenText™ eDirectory 9.2.3.0000.
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 · moderate confidenceCross-site scripting (XSS) vulnerability in OpenText eDirectory 9.2.3.0000 allows unauthenticated remote attackers to inject malicious scripts into web pages generated by the application due to improper input neutralization.
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< 9.2.3.0000CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Identify if eDirectory is installedCheck for eDirectory installation directories (commonly under /opt/novell/eDirectory or C:\Novell\eDirectory on Windows) and look for ndsd or ndsmanage processes runningAffected if eDirectory software is not found on the system
-
Determine installed eDirectory versionRun 'ndsconfig -v' or 'ndsmanage -v' from the eDirectory bin directory, or check the ndsvers.ini file in the eDirectory installation directory for the version numberAffected if The version number is lower than 9.2.3.0000 (e.g., 9.2.2.x, 9.1.x, etc.)
-
Check if web components are enabledInspect the nds.conf or ndsmanagement.xml configuration files in the eDirectory data directory for web server module configurations (HTTP/HTTPS listeners)Affected if HTTP or HTTPS web listeners are configured and enabled for eDirectory administration or iManager
-
Verify web interface accessibilityAttempt to access the eDirectory iManager or admin web interface on the configured HTTP/HTTPS ports (typically 8080 or 8443) from a browserAffected if The web interface is accessible and accepts user input that could be reflected in pages without proper encoding
System is affected if eDirectory version is below 9.2.3.0000 AND the web administration interface (iManager or similar) is enabled and accessible.
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.
dbcve · scoped9.2.3.0000
Apply vendor-supplied patch or upgrade to a patched version of eDirectory. If immediate patching is not possible, implement output encoding and input validation as compensating controls.
eDirectory 9.2.3.0000
- Identify the current eDirectory version by checking the server or documentation
- Download eDirectory 9.2.3.0000 or later from the OpenText/NetIQ official portal
- Review the upgrade documentation for eDirectory 9.2.3.0000
- Perform a backup of the current eDirectory configuration and data
- Execute the upgrade following the official upgrade procedure
- Verify the upgrade was successful and the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22503 — 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-2021-22503 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