Provisioning ServicesApplication · Citrix
CVE-2016-9679
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 Provisioning Services before 7.12 allows attackers to execute arbitrary code by overwriting a function pointer.
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 confidenceMemory corruption vulnerability in Citrix Provisioning Services allowing an attacker to overwrite a function pointer and achieve arbitrary code execution. This is a critical write-what-where condition enabling complete system compromise.
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
Provisioning ServicesApplication
= 7.0= 7.1= 7.6= 7.7= 7.8= 7.9= 7.11CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Citrix Provisioning Services installationLocate the Citrix Provisioning Services installation directory, typically found in C:\Program Files\Citrix\Provisioning Services or C:\Program Files (x86)\Citrix\Provisioning Services. Check for the executable BNImage.exe or the PVS service.Affected if The software is installed in the specified paths
-
Determine the installed versionRight-click on BNImage.exe or the main provisioning executable, select Properties, and check the File Version field. Alternatively, open the Windows Registry editor and navigate to HKLM\SOFTWARE\Citrix\ProvisioningServices to find the InstalledVersion value.Affected if The version matches any of the following: 7.0, 7.1, 7.6, 7.7, 7.8, 7.9, or 7.11
-
Verify the PVS service is presentOpen Windows Services (services.msc) and locate the Citrix Provisioning Services service (commonly named 'CitrixProvisioningService' or 'BNService'). Confirm the service exists and is running.Affected if The service exists and the associated binaries are from an affected version listed above
You are affected if Citrix Provisioning Services is installed and the version is 7.0, 7.1, 7.6, 7.7, 7.8, 7.9, or 7.11.
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.
dbcve · scopedUpgrade Citrix Provisioning Services to version 7.12 or later to remediate this vulnerability.
7.12 or later
- Backup the current Citrix Provisioning Services configuration and database
- Download Citrix Provisioning Services version 7.12 or later from the official Citrix download portal
- Review the Citrix upgrade documentation for version 7.12
- Execute the upgrade installer on the Provisioning Services server
- Verify the upgrade was successful and services are running
- Test that provisioning functionality works correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Provisioning Services
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9679 — 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-9679 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