CVE-2011-2759
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 login page of IDSWebApp in the Web Administration Tool in IBM Tivoli Directory Server (TDS) 6.2 before 6.2.0.3-TIV-ITDS-IF0004 does not have an off autocomplete attribute for authentication fields, which makes it easier for remote attackers to obtain access by leveraging an unattended workstation.
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 confidenceThe login page of IDSWebApp in IBM Tivoli Directory Server 6.2 Web Administration Tool does not include the autocomplete='off' attribute on username and password input fields. This allows web browsers to cache credentials, enabling attackers with physical or shared access to retrieve stored credentials from the browser's auto-complete history.
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= 6.2.0.0= 6.2.0.1= 6.2.0.2CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 if IDSWebApp is deployedLocate the IDSWebApp web application in your IBM TDS installation directory or confirm it is accessible via the web administration URL (typically /IDSWebApp/idsNav).Affected if The IDSWebApp is installed and accessible on the system.
-
Check IBM TDS versionRun 'ibmditool -version' or check the installation manifest/version file to determine the exact IBM Tivoli Directory Server version installed.Affected if The installed version is 6.2, 6.2.0.0, 6.2.0.1, or 6.2.0.2.
-
Access the IDSWebApp login pageNavigate to the IDSWebApp login URL (such as https://hostname/IDSWebApp/idsNav) using a web browser to retrieve the login form HTML.Affected if The login page is accessible and returns HTML content.
-
Inspect login form input fields for autocomplete attributeView the page source or use browser developer tools to examine the HTML for the username and password input elements. Check if both input fields include the attribute autocomplete='off'.Affected if The username input field and password input field do NOT contain autocomplete='off' in their HTML tags.
A system is affected if IBM TDS version 6.2.x (specifically 6.2, 6.2.0.0, 6.2.0.1, or 6.2.0.2) is running with IDSWebApp and the login form's username and password input fields lack the autocomplete='off' attribute.
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 dataAdd the autocomplete='off' attribute to both the username and password input fields in the IDSWebApp login form HTML, or upgrade to IBM TDS 6.2.0.3-TIV-ITDS-IF0004 or later if a vendor patch is available.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2759 — 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-2011-2759 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