CVE-2007-1196
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 · uneditedUnspecified vulnerability in Citrix Presentation Server Client for Windows before 10.0 allows remote web sites to execute arbitrary code via unspecified vectors, related to the implementation of ICA connectivity through proxy servers.
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 a remote code execution vulnerability in the Citrix Presentation Server Client for Windows (versions prior to 10.0). The flaw exists in how the client handles ICA connectivity through proxy servers, allowing malicious web sites to potentially execute arbitrary code on affected Windows clients.
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<= 9.200CVSS 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.
-
Verify Citrix Presentation Server Client installationOpen Windows Control Panel and look for 'Citrix Presentation Server Client' or 'Citrix ICA Client' in the list of installed programs, or check the program directory (typically C:\Program Files\Citrix) for Citrix client executablesAffected if Citrix Presentation Server Client is not installed on the system
-
Determine the installed client versionRight-click the Citrix client executable (commonly wfcrun32.exe or pn.exe) in the Program Files\Citrix folder, select Properties, and view the Version tab. Alternatively, open a command prompt and run 'wfcrun32.exe -version' if availableAffected if The displayed version number is 9.200 or lower (including 9.x versions prior to 9.200)
-
Check for ICA proxy connectivity configurationOpen the Citrix Connection Manager or ICA Client settings (typically accessible from the Windows Start menu under Citrix programs), then locate the proxy or network settings configuration panel. Look for any proxy server settings that enable ICA traffic to route through proxy serversAffected if Proxy settings are configured and enabled for ICA connections - this is the specific configuration path through which the vulnerability can be exploited
A system is affected if it has Citrix Presentation Server Client version 9.200 or earlier installed with proxy settings enabled for ICA connectivity, allowing malicious web sites to potentially execute arbitrary code through the client.
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 Presentation Server Client for Windows to version 10.0 or later. Until patched, restrict user access to untrusted websites and ensure proper network segmentation around Citrix infrastructure.
Citrix Presentation Server Client 10.0 or later
- 1. Identify all systems running Citrix Presentation Server Client for Windows version 9.200 or earlier
- 2. Download Citrix Presentation Server Client version 10.0 or later from the official Citrix website
- 3. Test the upgrade in a non-production environment first
- 4. Deploy the upgrade to production systems following standard change management procedures
- 5. Verify the client version post-upgrade by checking the client properties or ICA file handling
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1196 — 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-2007-1196 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