CVE-2011-4042
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 · uneditedAn unspecified ActiveX control in SVUIGrd.ocx in ARC Informatique PcVue 6.0 through 10.0, FrontVue, and PlantVue allows remote attackers to execute arbitrary code by using a crafted HTML document to obtain control of 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 confidenceAn unspecified ActiveX control (SVUIGrd.ocx) in ARC INFORMATIQUE PcVue 6.0 through 10.0, FrontVue, and PlantVue allows remote attackers to execute arbitrary code via a crafted HTML document that manipulates a function pointer, enabling vtable hijacking and code execution.
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 dataall versions>= 6.0, <= 10.0all versionsCVSS 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.
-
Locate SVUIGrd.ocx on the systemSearch for SVUIGrd.ocx in typical installation directories such as C:\Program Files\ArcInfo or C:\Program Files\PcVue, and in the Windows\System32 directory. Use the command: dir /s C:\SVUIGrd.ocxAffected if The file SVUIGrd.ocx exists on the system
-
Check ActiveX control registrationOpen Registry Editor and look for the CLSID of SVUIGrd.ocx under HKEY_CLASSES_ROOT\CLSID. The typical CLSID for this control should be searched in registry keys under HKEY_CLASSES_ROOT\TypeLib and HKEY_CLASSES_ROOT\SVUIGrdAffected if The ActiveX control is registered in the Windows registry
-
Verify if killbit is set for the controlCheck the registry path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{CLSID} for the SVUIGrd.ocx control. If the Compatibility Flags value is set to 0x00000400, the killbit is set (control disabled). Check both HKLM and HKCU paths.Affected if Killbit is NOT set (the control is allowed to run in Internet Explorer)
-
Determine installed PcVue versionCheck the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Arcinfo\PcVue\Version or look in Add/Remove Programs for Arcinfo PcVue installations. The version number will be displayed.Affected if Installed version is between 6.0 and 10.0 inclusive
-
Check for FrontVue or PlantVue installationsSearch registry under HKEY_LOCAL_MACHINE\SOFTWARE\Arcinfo for FrontVue or PlantVue entries, or check Add/Remove Programs for these product names.Affected if Either FrontVue or PlantVue is installed (all versions are affected)
The system is affected if SVUIGrd.ocx is present, the ActiveX control is registered, the killbit is not set to disable it, and any version of PcVue 6.0-10.0, FrontVue, or PlantVue is installed.
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 dataDisable the SVUIGrd.ocx ActiveX control in Internet Explorer via killbit or Group Policy, restrict web browsing to trusted zones only, and apply vendor patches when available.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4042 — 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-2011-4042 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