Skip to content
Fencer Intel
critical 10.0

CVE-2013-3075 in the critical feed json

Multiple buffer overflows in ActUWzd.dll 1.0.0.1 in Mitsubishi MX Component 3, as distributed in Citect CitectFacilities 7.10 and CitectSca…

published 13y ago modified 4mo ago also EUVD-2013-3013

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
10.8%
EPSS 10.8% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

Multiple 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.

Is CVE-2013-3075 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-13-140-01 updated cvss 9.3

Mitsubishi Electric Automation MX Component V3 ActiveX Vulnerability

  • Mitsubishi Electric Automation MX Component 3 Mitsubishi Electric CitectFacilities <=v7.10 Mitsubishi Electric CitectSCADA <=v7.0
    affected: mitigation

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Timeline

  1. First public exploit (EDB-24886)
  2. Published

Exploit prediction

10.77% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-24886 Mitsubishi MX ActiveX Component 3 - 'ActUWzd.dll' 'WzTitle' Remote Heap Spray remote, 2013-03-25

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.