CVE-2010-2193
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 · uneditedMultiple unspecified vulnerabilities in the CA (1) PSFormX and (2) WebScan ActiveX controls, as distributed on the CA Global Advisor web site until May 2009, allow remote attackers to execute arbitrary code via unknown 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 confidenceMultiple critical vulnerabilities exist in CA PSFormX and WebScan ActiveX controls distributed on the CA Global Advisor website until May 2009. These unspecified flaws allow remote attackers to execute arbitrary code on affected systems. The CVSS 10 score indicates complete compromise of confidentiality, integrity, and availability.
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= 56393399-041a-4650-94c7-13dfcb1f4665= 7b297bfd-85e4-4092-b2af-16a91b2ea103CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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.
-
Check registry for PSFormX ActiveX controlOpen Windows Registry Editor and navigate to HKEY_CLASSES_ROOT\CLSID\{56393399-041a-4650-94c7-13dfcb1f4665} to see if this PSFormX control is registeredAffected if The registry key exists, indicating the vulnerable PSFormX ActiveX control is installed
-
Check registry for WebScan ActiveX controlOpen Windows Registry Editor and navigate to HKEY_CLASSES_ROOT\CLSID\{7b297bfd-85e4-4092-b2af-16a91b2ea103} to see if this WebScan control is registeredAffected if The registry key exists, indicating the vulnerable WebScan ActiveX control is installed
-
Search for PSFormX files on diskUse Windows Search or file explorer to look for files named PSFormX.* or containing PSFormX in the filename, particularly in System32, SysWOW64, or Program Files directoriesAffected if Any PSFormX-related .ocx or .dll files are found on the system
-
Search for WebScan files on diskUse Windows Search or file explorer to look for files named WebScan.* or containing WebScan in the filename, particularly in System32, SysWOW64, or Program Files directoriesAffected if Any WebScan-related .ocx or .dll files are found on the system
If either the PSFormX (56393399-041a-4650-94c7-13dfcb1f4665) or WebScan (7b297bfd-85e4-4092-b2af-16a91b2ea103) ActiveX control is found registered or present as files, the system is affected by this CVE.
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 dataSince these ActiveX controls are from discontinued 2009-era software, the primary remediation is to identify and remove any instances of the vulnerable PSFormX and WebScan ActiveX controls from systems, or implement network-level blocks to prevent their loading.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2193 — 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-2010-2193 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