Xenmobile ServerOperating system · Citrix
CVE-2017-9231
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 · uneditedXML external entity (XXE) vulnerability in Citrix XenMobile Server 9.x and 10.x before 10.5 RP3 allows attackers to obtain sensitive information via unspecified vectors.
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 confidenceThis is an XML External Entity (XXE) injection vulnerability in Citrix XenMobile Server versions 9.x and 10.x before 10.5 RP3. The vulnerability allows attackers to inject malicious XML payloads that can be parsed by the application, potentially allowing unauthorized access to local files, internal resources, or sensitive information through crafted entity references.
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 ServerOperating system
= 9.0= 10.0= 10.1= 10.3= 10.3.5= 10.3.6= 10.4= 10.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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Identify if Citrix XenMobile Server is deployedLocate the XenMobile Server installation directory or check running services for the XenMobile processAffected if The server is installed and running but the version cannot be determined or is below 10.5 RP3
-
Determine the installed XenMobile Server versionAccess the XenMobile admin console and navigate to the version information page, or use the system command to retrieve the installed build numberAffected if The version is 9.0, 10.0, 10.1, 10.3, 10.3.5, 10.3.6, 10.4, or 10.5 (any version before 10.5 RP3)
-
Verify the XML parser configurationInspect the XML parser configuration files or settings that handle XML input processing within the XenMobile ServerAffected if External entity processing is enabled in the XML parser configuration
-
Review XML processing endpointsIdentify and examine the XML-handling endpoints or services within XenMobile that accept XML inputAffected if The application processes XML without disabling external entity resolution
A user is affected if XenMobile Server version 9.0 through 10.5 is installed and the XML parser has external entity processing enabled, allowing crafted XXE payloads to be processed.
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 Citrix XenMobile Server to version 10.5 RP3 or later. Additionally, ensure the XML parser is configured to disable external entity processing as a defense-in-depth measure.
Fix this in Xenmobile Server
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9231 — 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-9231 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