# CVE-2011-3330: Memory corruption in n/a

> A buffer overflow in Schneider Electric industrial software allows local users to execute arbitrary code via a system parameter.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Nov 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-phg6-j5pg-w4c8

## What is CVE-2011-3330?

CVE-2011-3330 is a high-severity memory corruption vulnerability in n/a, published on 4 Nov 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2011-3330?

It affects 6 products.


Products: Schneider-Electric Monitor Pro, Schneider-Electric Opc Factory Server, Schneider-Electric Pl7 Pro, Schneider-Electric Telemecanique Driver Pack, Schneider-Electric Unity Pro, Schneider-Electric Vijeo Citect.

## How do I fix CVE-2011-3330?

No fix has been published for CVE-2011-3330 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-3330 being exploited?

There is no known exploitation of CVE-2011-3330 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3330 and fix it if it is affected.

What it is: CVE-2011-3330 is a high-severity memory corruption vulnerability in n/a, published on 4 Nov 2011. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-3330 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-3330/ (Markdown: https://insights.sbomify.com/CVE-2011-3330/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-3330
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-3330
- OSV: https://osv.dev/vulnerability/CVE-2011-3330

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-3330/
Summaries are generated and may contain mistakes; the official description above is the record.