CVE-2013-6742
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 Meeting Server in IBM Sametime 8.5.2 through 8.5.2.1 and 9.x through 9.0.0.1 do not have an off autocomplete attribute for a password field, 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 IBM Sametime Meeting Server versions 8.5.2-8.5.2.1 and 9.x-9.0.0.1 fail to set autocomplete='off' on password form fields. This allows web browsers to cache credentials, which can be harvested by attackers with physical access to unattended workstations.
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= 8.5.2.0= 8.5.2.1= 9.0.0.0= 9.0.0.1CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 IBM Sametime Meeting Server installationLocate the Sametime Meeting Server installation directory or check for running services on common ports (8080, 443, 80). Typical install paths on Windows: C:\Program Files\IBM\Sametime\MeetingServer or /opt/IBM/Sametime on Linux.Affected if The software is not installed or not running as a meeting server.
-
Determine installed versionCheck the version of the IBM Sametime Meeting Server by inspecting version files in the installation directory, or access the server admin interface and look for version information in the About or System Info section.Affected if Version matches 8.5.2.0, 8.5.2.1, 9.0.0.0, or 9.0.0.1.
-
Access login or meeting join pageOpen a web browser and navigate to the Sametime Meeting Server login page, typically at https://hostname/meeting or https://hostname/stmeeting. View the page source (right-click > View Page Source) or use browser developer tools (F12) to inspect form elements.Affected if The server is reachable and exposes login or meeting join forms.
-
Inspect password input fields for autocomplete attributeIn the page source or developer tools, locate all <input type='password'> elements. Check whether each has the attribute autocomplete='off' or autocomplete='new-password'. Look specifically in login forms and meeting join/authentication forms.Affected if Password input fields do NOT have autocomplete='off' or autocomplete='new-password' attribute present.
User is affected if IBM Sametime Meeting Server version is 8.5.2.0, 8.5.2.1, 9.0.0.0, or 9.0.0.1 AND password form fields on the login/meeting pages 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 autocomplete='off' attribute to all password input fields in the login/meeting server forms, and implement aggressive session timeout policies as a defense-in-depth measure.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6742 — 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-2013-6742 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