CVE-2010-0814
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 Microsoft Access Wizard Controls in ACCWIZ.dll in Microsoft Office Access 2003 SP3 and 2007 SP1 and SP2 do not properly interact with the memory-allocation approach used by Internet Explorer during instantiation, which allows remote attackers to execute arbitrary code via a web site that references multiple ActiveX controls, as demonstrated by the ImexGrid and FieldList controls, aka "Access ActiveX Control Vulnerability."
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 confidenceThis is a memory corruption vulnerability in Microsoft Access ActiveX controls (ACCWIZ.dll, specifically ImexGrid and FieldList controls) where improper interaction with Internet Explorer's memory-allocation approach during instantiation allows remote code execution via malicious web pages.
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= 2003= 2007CVSS 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.
-
Check installed Microsoft Access versionOpen Access, go to Help > About Microsoft Office Access, or check the version in Add/Remove ProgramsAffected if Version is 2003 (11.0) or 2007 (12.0)
-
Locate ACCWIZ.dll on the systemSearch for ACCWIZ.dll in typical Office installation paths such as C:\Program Files\Microsoft Office\Office11\ACCWIZ.dll (Office 2003) or C:\Program Files\Microsoft Office\Office12\ACCWIZ.dll (Office 2007)Affected if The file exists in these paths indicating the vulnerable DLL is present
-
Verify ActiveX control registrationCheck Windows registry under HKLM\SOFTWARE\Classes\TypeLib for entries related to ImexGrid or FieldList controls, or use regsvr32 to query ACCWIZ.dll registration statusAffected if The ImexGrid or FieldList ActiveX controls are registered on the system
-
Check Internet Explorer ActiveX settingsIn Internet Explorer, go to Tools > Internet Options > Security > Custom Level, and examine settings under ActiveX controls and plugins section for the specific controlsAffected if ActiveX controls from ACCWIZ.dll are set to Enabled or Prompt rather than Disabled
User is affected if Microsoft Access 2003 or 2007 is installed, ACCWIZ.dll is present, and the ImexGrid/FieldList ActiveX controls are registered and enabled in Internet Explorer.
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 · scopedDisable the vulnerable ActiveX controls in Internet Explorer settings or deploy the Microsoft security update to upgrade to a patched version of Microsoft Office Access.
Microsoft Office Access 2007 SP3 or later (which includes the security fix)
- 1. Apply Microsoft security update MS10-044 which addresses this Access ActiveX vulnerability
- 2. For Access 2003 SP3: Install security update KB981355 from Microsoft Update
- 3. For Access 2007 SP1/SP2: Install security update KB981355 from Microsoft Update
- 4. After applying the update, verify ACCWIZ.dll version has been updated
- 5. Restart Internet Explorer if it was open during the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0814 — 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-0814 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