dbcve.org
Monitor ProApplication · Schneider Electric

CVE-2011-3330

HIGH · 7.2 CVSS v2.0 Published 2011-11-04
Fix available
A fix is available. Upgrade to after 7.20 or later.
See remediation →
77/100
Remediation priority · High
No privileges Zero-click

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 · unedited
Buffer overflow in the UnitelWay Windows Device Driver, as used in Schneider Electric Unity Pro 6 and earlier, OPC Factory Server 3.34, Vijeo Citect 7.20 and earlier, Telemecanique Driver Pack 2.6 and earlier, Monitor Pro 7.6 and earlier, and PL7 Pro 4.5 and earlier, allows local users, and possibly remote attackers, to execute arbitrary code via an unspecified system parameter.

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 confidence

Buffer overflow vulnerability in the UnitelWay Windows Device Driver used across multiple Schneider Electric industrial software products (Unity Pro, OPC Factory Server, Vijeo Citect, etc.). The overflow occurs when processing an unspecified system parameter, allowing local users or potentially remote attackers to execute arbitrary code with elevated privileges.

MitigationApply vendor-supplied patches for affected products (Unity Pro 7+, OPC Factory Server 3.35+, Vijeo Citect 7.30+, Driver Pack 2.7+, Monitor Pro 7.7+, PL7 Pro 4.6+). If patches unavailable, implement network segmentation to limit exposure and restrict local user privileges.

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
Monitor ProApplication
Affected:<= 7.6
Opc Factory ServerApplication
Affected:<= 3.34
Pl7 ProApplication
Affected:<= 4.5
Telemecanique Driver PackApplication
Affected:<= 2.6
Unity ProApplication
Affected:<= 6.0
Vijeo CitectApplication
Affected:<= 7.20

CVSS 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
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Schneider Electric products
    Check Program Files or Program Files (x86) directories for folders named: Monitor Pro, Opc Factory Server, PL7 Pro, Driver Pack, Unity Pro, Vijeo Citect, or UnitelWay. Also check Windows Registry under HKLM\SOFTWARE\Schneider Electric or HKLM\SOFTWARE\Wow6432Node\Schneider Electric for installed product entries.
    Affected if Any of the six affected products (Monitor Pro, OPC Factory Server, PL7 Pro, Driver Pack, Unity Pro, Vijeo Citect) are found on the system
  2. Check Monitor Pro version
    Look for Monitor Pro in installed programs list or check version info on the main executable (typically in C:\Program Files\Schneider Electric\Monitor Pro\ or similar path). Compare version number to 7.6.
    Affected if Monitor Pro version is 7.6 or lower
  3. Check OPC Factory Server version
    Look for OPC Factory Server in installed programs list or check version info on OFS executable. Compare version number to 3.34.
    Affected if OPC Factory Server version is 3.34 or lower
  4. Check Unity Pro version
    Look for Unity Pro in installed programs list or check version info on Unity Pro executable. Compare version number to 6.0.
    Affected if Unity Pro version is 6.0 or lower
  5. Check Vijeo Citect version
    Look for Vijeo Citect in installed programs list or check version info on Citect executable. Compare version number to 7.20.
    Affected if Vijeo Citect version is 7.20 or lower
  6. Verify UnitelWay driver presence
    Check for UnitelWay driver files (utlwy*.sys) in Windows\System32\drivers\ or within the product installation directories. The driver is the vulnerable component regardless of which product installed it.
    Affected if UnitelWay Windows Device Driver files exist on the system

A system is affected if any of the six listed Schneider Electric products are installed with versions at or below the affected thresholds, or if the UnitelWay driver component is present on the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 7.20
Interim mitigation

Apply vendor-supplied patches for affected products (Unity Pro 7+, OPC Factory Server 3.35+, Vijeo Citect 7.30+, Driver Pack 2.7+, Monitor Pro 7.7+, PL7 Pro 4.6+). If patches unavailable, implement network segmentation to limit exposure and restrict local user privileges.

Fix this in Monitor Pro Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA4.0 h
40.0 hours of engineering $6,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,008.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-3330 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-3330 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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