CVE-2015-1977
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 · uneditedDirectory traversal vulnerability in the Web Administration tool in IBM Tivoli Directory Server (ITDS) before 6.1.0.74-ISS-ISDS-IF0074, 6.2.x before 6.2.0.50-ISS-ISDS-IF0050, and 6.3.x before 6.3.0.43-ISS-ISDS-IF0043 and IBM Security Directory Server (ISDS) before 6.3.1.18-ISS-ISDS-IF0018 and 6.4.x before 6.4.0.9-ISS-ISDS-IF0009 allows remote attackers to read arbitrary files via a .. (dot dot) in a URL.
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 confidenceDirectory traversal vulnerability in the Web Administration tool of IBM Tivoli Directory Server (ITDS) and IBM Security Directory Server (ISDS) allows remote attackers to read arbitrary files on the system by using '..' (dot-dot) sequences in URLs. This is a high-severity (CVSS 7.5) issue enabling unauthenticated file disclosure.
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= 6.2.0= 6.2.0.0= 6.2.0.1= 6.2.0.2= 6.2.0.3= 6.2.0.4= 6.2.0.5= 6.2.0.6= 6.2.0.7= 6.2.0.8= 6.2.0.10= 6.2.0.11= 6.4.0= 6.4.0.0= 6.4.0.1= 6.4.0.2= 6.4.0.3= 6.4.0.4= 6.4.0.5= 6.4.0.6= 6.4.0.7= 6.4.0.8= 6.3.1= 6.3.1.0CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the installed IBM directory server productLocate the installed product name and version. This can typically be found in the IBM installation directory, or by querying the product via command line (for example, using 'idsversion' or checking the installation logs). Compare the result to the affected product list: IBM Tivoli Directory Server (ITDS) 6.2.0.x or IBM Security Directory Server (ISDS) 6.3.1.x or 6.4.0.x.Affected if The installed product is ITDS version 6.2.0, 6.2.0.0 through 6.2.0.11, or ISDS version 6.3.1, 6.3.1.0 through 6.3.1.1, or ISDS version 6.4.0, 6.4.0.0 through 6.4.0.8.
-
Confirm the exact version numberRetrieve the precise installed version number (for example, 6.2.0.5 or 6.4.0.4). Check the version against the specific affected versions listed: ITDS = 6.2.0, 6.2.0.0, 6.2.0.1, 6.2.0.2, 6.2.0.3, 6.2.0.4, 6.2.0.5, 6.2.0.6, 6.2.0.7, 6.2.0.8, 6.2.0.10, 6.2.0.11; ISDS = 6.4.0, 6.4.0.0, 6.4.0.1, 6.4.0.2, 6.4.0.3, 6.4.0.4, 6.4.0.5, 6.4.0.6, 6.4.0.7, 6.4.0.8, 6.3.1, 6.3.1.0.Affected if The exact version matches one of the versions listed in the affected versions list.
-
Verify if the Web Administration interface is enabledCheck whether the Web Administration tool (web-based admin console) is currently enabled and accessible on the system. This is typically configured in the IBM Directory Server configuration files or through the administration daemon status. The vulnerability exists in the Web Administration component specifically.Affected if The Web Administration interface is enabled and network-accessible.
-
Check network exposure of the admin interfaceDetermine if the Web Administration port (default HTTP port 9080 or HTTPS port 9443 for IBM ITDS/ISDS) is exposed to the network or internet. Review firewall rules, bind addresses in configuration, and any ACL settings controlling access to the admin URLs.Affected if The Web Administration interface is reachable from untrusted network segments or the internet.
The system is affected if it runs any of the listed affected versions of IBM Tivoli Directory Server or IBM Security Directory Server AND has the Web Administration interface enabled and accessible, allowing an unauthenticated remote attacker to exploit the directory traversal flaw via specially crafted URLs containing '..' sequences.
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 appropriate IBM interim fix (IF) for the specific version: ITDS 6.1.0.74-IF0074, 6.2.0.50-IF0050, 6.3.0.43-IF0043, or ISDS 6.3.1.18-IF0018, 6.4.0.9-IF0009. If patching is not immediately possible, consider restricting network access to the Web Administration interface via firewall or ACLs.
- 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-2015-1977 — 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-2015-1977 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