CVE-2013-3075
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 buffer overflows in ActUWzd.dll 1.0.0.1 in Mitsubishi MX Component 3, as distributed in Citect CitectFacilities 7.10 and CitectScada 7.10r1, allow remote attackers to execute arbitrary code via a long string, as demonstrated by a long WzTitle property value to a certain ActiveX control.
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 confidenceBuffer overflow vulnerability in ActUWzd.dll (v1.0.0.1), a Mitsubishi MX Component 3 ActiveX control distributed with Citect CitectFacilities 7.10 and CitectScada 7.10r1. Attackers can exploit via long WzTitle property values to achieve arbitrary 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 data= 3= 7.10= 7.10CVSS 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.
-
Locate ActUWzd.dll on the systemSearch for the file ActUWzd.dll in common installation directories (such as C:\Windows\System32, C:\Program Files, or product-specific directories for Mitsubishi MX Component or Citect installations) and note its full pathAffected if The DLL exists on the system at any location
-
Verify the DLL versionRight-click the DLL file, select Properties, and check the File Version field under the Version tab. Compare this version to 1.0.0.1Affected if File version is 1.0.0.1 or if the version field is missing/empty when the DLL is present
-
Identify installed Mitsubishi MX ComponentCheck installed programs via Control Panel > Programs and Features, or check registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Mitsubishi for MX Component installation and versionAffected if Mitsubishi MX Component version 3 is installed
-
Identify installed Citect productsCheck installed programs via Control Panel > Programs and Features, or check registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Schneider Electric\Citect for CitectFacilities or CitectSCADA and their versionsAffected if CitectFacilities 7.10 or CitectSCADA 7.10 (or 7.10r1) is installed
-
Check if ActiveX control is registeredSearch Windows registry under HKEY_CLASSES_ROOT for CLSID entries related to ActUWzd or Mitsubishi MX Component ActiveX controls, or use regsvr32 to query the DLL registration statusAffected if The ActiveX control is registered and loadable by browsers or vulnerable applications
A system is affected if ActUWzd.dll version 1.0.0.1 is present AND any of the affected products (Mitsubishi MX Component 3, CitectFacilities 7.10, or CitectSCADA 7.10) are installed and the ActiveX control is registered.
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 dataApply available patches from Mitsubishi and/or Schneider Electric (Citect) for MX Component and affected Citect products; consider network segmentation to limit exposure of SCADA systems if patches are unavailable.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3075 — 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-2013-3075 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