dbcve.org
Directory ServicesApplication · Opentext

CVE-2023-7249

CRITICAL · 9.8 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to 24.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in OpenText OpenText Directory Services allows Path Traversal.This issue affects OpenText Directory Services: from 16.4.2 before 24.1.

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

Path traversal vulnerability in OpenText Directory Services allows attackers to access files outside restricted directories via specially crafted path inputs. The vulnerability affects versions 16.4.2 through versions before 24.1 and carries a critical CVSS score of 9.8, indicating potential for complete system compromise.

MitigationUpgrade to OpenText Directory Services version 24.1 or later to remediate this vulnerability. Apply input validation and restrict file system access controls as interim measures if immediate patching is not feasible.

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
Directory ServicesApplication
Affected:>= 16.4.2, < 24.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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 OpenText Directory Services is installed
    Check for the OpenText Directory Services process or service running on the system. On Windows, look for services named 'OpenText Directory Services' or process 'otds' in Task Manager. On Linux, check for 'otds' or 'directory-services' processes.
    Affected if The OpenText Directory Services process or service is found running on the system
  2. Determine the installed version
    Locate the OpenText Directory Services installation directory and look for a version file or check the product information. Common locations include the installation root folder for a 'version' or 'product.info' file, or run: otds --version if the command-line tool is available.
    Affected if The version returned is >= 16.4.2 and < 24.1
  3. Check if the web service component is exposed
    Identify if the OpenText Directory Services web interface or API endpoint is accessible externally. Review network configuration and firewall rules for ports typically used by the service (default HTTP/HTTPS ports). Look for entries in web server configuration files that map to the Directory Services application.
    Affected if The web service port is open and accessible to network users or external attackers
  4. Identify path traversal access points
    Review the Directory Services configuration for endpoints that accept file or directory path parameters. Check web.xml or similar configuration files for servlet mappings that handle file requests. Look for parameters that might accept 'path', 'file', 'directory', or similar input names.
    Affected if Endpoints accepting user-supplied path parameters are found in the configuration and accessible without additional authentication barriers

You are affected if OpenText Directory Services version is 16.4.2 or higher but below 24.1 AND the web service component is accessible, allowing path traversal attacks via crafted input to file/directory handling endpoints.

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
Upgrade available Upgrade to 24.1 or later
Fixed in 24.1
Interim mitigation

Upgrade to OpenText Directory Services version 24.1 or later to remediate this vulnerability. Apply input validation and restrict file system access controls as interim measures if immediate patching is not feasible.

Recommended fix High confidence

24.1

  1. 1. Back up the current OpenText Directory Services installation and configuration.
  2. 2. Consult the OpenText Directory Services 24.1 release notes for any pre-upgrade requirements or migration steps.
  3. 3. Download OpenText Directory Services version 24.1 or later from the official OpenText support portal (support.opentext.com).
  4. 4. Stop the Directory Services instance.
  5. 5. Perform the upgrade by following the official installation/upgrade instructions for version 24.1.
  6. 6. Verify the upgrade was successful by checking the version number and ensuring services start properly.
  7. 7. Test that normal directory services operations function correctly.
Caveat Check release notes for version 24.1 for any configuration or compatibility changes

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

Fix this in Directory Services Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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