CVE-2015-1975
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 · uneditedThe web administration tool in IBM Tivoli Security Directory Server 6.0 before iFix 75, 6.1 before iFix 68, 6.2 before iFix 44, and 6.3 before iFix 37 and IBM Security Directory Server 6.3.1 before iFix 11 and 6.4 before iFix 2 allows local users to gain privileges via vectors related to argument injection. IBM X-Force ID: 103694.
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 confidenceLocal privilege escalation vulnerability in the web administration tool of IBM Tivoli Security Directory Server and IBM Security Directory Server allows local users to inject arguments and gain elevated privileges. The vulnerability affects multiple versions across 6.0, 6.1, 6.2, 6.3, 6.3.1, and 6.4 before their respective iFixes.
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.0= 6.1.0= 6.2.0.0= 6.3.0.0= 6.3.1.0= 6.4.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if IBM Tivoli Directory Server is installedLook for the product installation directory, commonly under /opt/ibm/tdi or /opt/ibm/ldap, or check for the 'IBMDirectoryServer' process running on the system.Affected if The product is present on the system.
-
Determine the installed versionCheck the version of the installed IBM Tivoli Directory Server or IBM Security Directory Server. Common locations include: running 'idsversion' command if available, checking installation logs, or looking for version files in the installation directory.Affected if The installed version matches 6.0, 6.1.0, 6.2.0.0, 6.3.0.0, 6.3.1.0, or 6.4.0 without the corresponding iFix applied.
-
Verify the web administration tool is accessibleCheck if the web-based administration interface (typically accessible via HTTP/HTTPS on port 8080, 8443, or similar) is running or configured on the system.Affected if The web administration tool is enabled and accessible to local users.
-
Check local user access to the systemIdentify local user accounts on the system that have access to interact with the IBM Directory Server environment.Affected if Local unprivileged users exist who could potentially exploit the argument injection vulnerability.
A user is affected if IBM Tivoli Directory Server or IBM Security Directory Server version 6.0, 6.1.0, 6.2.0.0, 6.3.0.0, 6.3.1.0, or 6.4.0 is installed without the corresponding iFix (iFix 75, 68, 44, 37, 11, or 2 respectively), and the web administration tool is accessible to local users.
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 vendor-supplied iFixes (iFix 75 for 6.0, iFix 68 for 6.1, iFix 44 for 6.2, iFix 37 for 6.3, iFix 11 for 6.3.1, and iFix 2 for 6.4) to patch the argument injection vulnerability in the web administration tool.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1975 — 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-1975 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