Xenmobile ServerApplication · Citrix
CVE-2016-6877
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 · uneditedCitrix XenMobile Server before 10.5.0.24 allows man-in-the-middle attackers to trigger HTTP 302 redirections via vectors involving the HTTP Host header and a cached page. NOTE: the vendor reports "our internal analysis of this issue concluded that this was not a valid vulnerability" because an exploitation scenario would involve a man-in-the-middle attack against a TLS session
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 vulnerability in Citrix XenMobile Server before 10.5.0.24 allows man-in-the-middle attackers to manipulate HTTP 302 redirections via vectors involving the HTTP Host header and cached pages. An attacker positioned on the network could potentially redirect users to malicious sites by exploiting how the server handles Host headers in cached response scenarios. The vendor disputes this as a valid finding, noting exploitation requires an already-compromised TLS session.
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
Xenmobile ServerApplication
<= 10.3.6.310CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/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.
-
Confirm Citrix XenMobile Server is installedIdentify if the target system is running Citrix XenMobile Server by reviewing installed software, service listings, or checking the application URL/interfaceAffected if The system is running XenMobile Server
-
Check the installed version numberAccess the XenMobile Server admin console or use system commands to retrieve the version. Compare the installed version against the affected range: any version <= 10.3.6.310 is potentially vulnerableAffected if Installed version is 10.3.6.310 or lower
-
Determine if HTTP access is enabledTest if the server responds on plain HTTP (port 80) in addition to HTTPS. Also check whether cached HTTP responses are being servedAffected if HTTP is accessible and caching is enabled, allowing manipulation of 302 redirects
-
Verify TLS configurationCheck whether mutual TLS (client certificate) authentication is enforced. Review SSL/TLS settings in the XenMobile Server configurationAffected if Mutual TLS authentication is NOT enforced, allowing a man-in-the-middle attacker to intercept traffic
The environment is affected if XenMobile Server version 10.3.6.310 or lower is installed AND the server allows HTTP access or does not enforce mutual TLS authentication, enabling a man-in-the-middle attacker to manipulate 302 redirections.
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 to XenMobile Server 10.5.0.24 or later. Ensure proper TLS certificate chain validation and mutual TLS authentication are enforced to prevent the MITM prerequisite attack vector.
Fix this in Xenmobile Server
Scoped from the published advisory
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6877 — 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-2016-6877 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