Unified Meetingplace Web Conferencing ServerApplication · Cisco
CVE-2013-1169
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 · uneditedCisco Unified MeetingPlace Web Conferencing Server 7.x before 7.1MR1 Patch 2, 8.0 before 8.0MR1 Patch 2, and 8.5 before 8.5MR3 Patch 1, when the Remember Me option is used, does not properly verify cookies, which allows remote attackers to impersonate users via a crafted login request, aka Bug ID CSCuc64846.
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 confidenceCisco Unified MeetingPlace Web Conferencing Server fails to properly verify cookies when the 'Remember Me' feature is enabled. This allows remote attackers to craft malicious login requests that bypass authentication and impersonate legitimate users by exploiting the improper cookie validation mechanism.
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
Unified Meetingplace Web Conferencing ServerApplication
= 7.1= 8.0= 8.5CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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.
-
Verify Cisco Unified MeetingPlace is installedCheck if the Cisco Unified MeetingPlace Web Conferencing Server application is running on the system or accessible via networkAffected if The product is present in the environment
-
Determine installed versionAccess the administrative interface or CLI to retrieve the exact version number of the installed Cisco Unified MeetingPlace Web Conferencing ServerAffected if Version is 7.1, 8.0, or 8.5 (exact match)
-
Check Remember Me feature statusLocate and inspect the authentication or login configuration settings within the MeetingPlace admin interface or configuration filesAffected if The Remember Me functionality is enabled or turned on
The environment is affected if Cisco Unified MeetingPlace Web Conferencing Server version 7.1, 8.0, or 8.5 is installed AND the Remember Me feature is currently enabled.
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.
dbcve · scopedUpgrade to version 7.1MR1 Patch 2, 8.0MR1 Patch 2, 8.5MR3 Patch 1 or later. As a temporary workaround, disable the 'Remember Me' functionality until patches can be applied.
7.1MR1 Patch 2 / 8.0MR1 Patch 2 / 8.5MR3 Patch 1 (depending on major version branch)
- 1. Identify the currently installed version of Cisco Unified MeetingPlace Web Conferencing Server
- 2. For version 7.1.x: Upgrade to 7.1MR1 Patch 2 or later
- 3. For version 8.0.x: Upgrade to 8.0MR1 Patch 2 or later
- 4. For version 8.5.x: Upgrade to 8.5MR3 Patch 1 or later
- 5. After upgrade, verify the Remember Me functionality works correctly and test that cookie verification is properly enforced
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Unified Meetingplace Web Conferencing Server
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1169 — 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-1169 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