Telepresence Tc SoftwareOperating system · Cisco
CVE-2015-0697
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 · uneditedOpen redirect vulnerability in the login page in Cisco TC Software before 6.3-26 and 7.x before 7.3.0 on Cisco TelePresence Collaboration Desk and Room Endpoints devices allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via unspecified vectors, aka Bug ID CSCuq94980.
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 · moderate confidenceOpen redirect vulnerability in the login page of Cisco TC Software on TelePresence Collaboration Desk and Room Endpoints allows remote attackers to redirect authenticated or unauthenticated users to arbitrary external websites via unspecified vectors, facilitating phishing attacks.
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
Telepresence Tc SoftwareOperating system
= 6.0.0= 6.0.0-cucm= 6.0.1= 6.0.1-cucm= 6.0.2= 6.0_base= 6.1.0= 6.1.0-cucm= 6.1.1= 6.1.1-cucm= 6.1.2= 6.1.2-cucmCVSS 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
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/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 Cisco TC Software versionAccess the device admin interface or use the command line interface (CLI) via SSH or console. Run the command to display the software version, typically 'show version' or 'xCommand SystemUnit SoftwareInfo'. Compare the displayed version against the affected list: 6.0.0, 6.0.0-cucm, 6.0.1, 6.0.1-cucm, 6.0.2, 6.0_base, 6.1.0, 6.1.0-cucm, 6.1.1, 6.1.1-cucm, 6.1.2, 6.1.2-cucm.Affected if The installed version matches any version in the affected list.
-
Verify the web login page is accessibleAttempt to access the device login page via HTTPS on the configured management IP address (typically port 443). Check if the /login.html or root endpoint responds with a login form.Affected if The web interface is exposed and the login page is reachable.
-
Inspect login page for redirect parametersReview HTTP requests and responses when accessing the login page. Look for URL parameters that control redirection, such as 'next', 'redirect', 'url', or 'dest'. Submit a test login request with a crafted redirect parameter pointing to an external domain, then verify if the response redirects to that external site.Affected if The login page accepts and acts upon redirect parameters that point to external domains outside the device's own domain.
The environment is affected if the Cisco TC Software version matches any of the listed affected versions AND the web login page is accessible and accepts external redirect parameters.
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 dataUpgrade Cisco TC Software to version 6.3-26 or later, or 7.3.0 or later, per Cisco advisory CSCuq94980. If immediate patching is not possible, monitor login page traffic for suspicious redirect parameters.
Fix this in Telepresence Tc Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0697 — 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-0697 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