Telepresence Server SoftwareApplication · Cisco
CVE-2017-3815
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 · uneditedAn API Privilege vulnerability in Cisco TelePresence Server Software could allow an unauthenticated, remote attacker to emulate Cisco TelePresence Server endpoints. Affected Products: This vulnerability affects Cisco TelePresence Server MSE 8710 Processors that are running a software release prior to Cisco TelePresence Software Release 4.3 and are running in locally managed mode. The vulnerable API was deprecated in Cisco TelePresence Software Release 4.3. More Information: CSCvc37616.
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 confidenceAn API privilege vulnerability in Cisco TelePresence Server MSE 8710 Processors allows unauthenticated remote attackers to emulate TelePresence Server endpoints. The vulnerability exists in software versions prior to 4.3 when the device is running in locally managed mode. The vulnerable API was deprecated in release 4.3.
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 Server SoftwareApplication
= 4.2\(4.17\)= 4.2\(4.18\)= 4.2\(4.19\)CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check installed Cisco TelePresence Server software versionAccess the device CLI or web interface and run 'show version' or navigate to the system information page to retrieve the installed software version numberAffected if Version is 4.2(4.17), 4.2(4.18), or 4.2(4.19) - versions prior to 4.3 are affected
-
Verify the device is running in locally managed modeAccess the device configuration or administration settings and check the management mode configuration. This is typically found under System > Settings or Admin > Management Mode in the web interface, or via 'show running-config' command in CLIAffected if Locally managed mode is enabled - this mode must be active for the vulnerability to be exploitable
-
Confirm the deprecated API is accessibleAttempt to access the API endpoint typically found at /putxml or similar administrative API paths used by TelePresence Server. Check if unauthenticated API requests are processed without authenticationAffected if The API responds to unauthenticated requests - this confirms the vulnerable deprecated API is still active
A system is affected if it runs Cisco TelePresence Server software version 4.2(4.17), 4.2(4.18), or 4.2(4.19) AND is configured in locally managed mode, as only this combination enables the vulnerable deprecated API.
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 TelePresence Server software to Release 4.3 or later, which deprecated the vulnerable API. If upgrade is not immediately possible, review and restrict locally managed mode configuration to reduce attack surface.
Fix this in Telepresence Server Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3815 — 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-2017-3815 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