XenappApplication · Citrix
CVE-2012-5161
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 · uneditedThe XML Service interface in Citrix XenApp 6.5 and 6.5 Feature Pack 1 allows remote attackers to execute arbitrary code 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 confidenceA pre-authentication remote code execution vulnerability in the XML Service interface of Citrix XenApp 6.5 allows unauthenticated remote attackers to execute arbitrary code via unspecified vectors. The XML Service handles XML requests for application provisioning and is exposed network-wide in typical deployments.
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
XenappApplication
= 6.5.0.0CVSS 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.
-
Identify XenApp versionCheck the installed version of Citrix XenApp by reviewing the program files or using the Citrix PowerShell commands (Get-XAServer or about_xenapp in farm)Affected if The installed version is exactly 6.5.0.0 (not patched with CP25 or later)
-
Verify XML Service is installedConfirm the XML Service role is installed on the server; check Windows Services for 'Citrix XML Service' or inspect the XenApp server configuration via Citrix Delivery Services ConsoleAffected if The XML Service is present on the server (this is required for exploitation)
-
Check if XML Service is running and listeningUse netstat or PowerShell to check if ports 80 or 443 are in LISTENING state on the XenApp server, as these are typical XML Service portsAffected if Ports 80 or 443 are bound and listening on the server (indicates XML Service is active)
-
Confirm network exposure of XML ServiceDetermine if the XML Service ports (80/443) are bound to all interfaces (0.0.0.0) rather than localhost only, by examining the XML Service configuration in the Citrix management tools or checking binding addressesAffected if The XML Service is bound to a network-accessible IP address, making it reachable from remote systems
You are affected if you are running XenApp 6.5.0.0 (without CP25 or later hotfix) AND the XML Service is enabled and exposed on network-accessible ports.
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 dataApply Citrix hotfix CP25 or later for XenApp 6.5; if the system is end-of-life, restrict network access to XML Service ports (typically 80/443) via firewall or IPSec, or migrate to a supported XenApp/XenDesktop version.
Fix this in Xenapp
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5161 — 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-2012-5161 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