# CVE-2010-4740: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a crafted CSV file in SCADA Engine BACnet OPC Client, requiring user interaction to open the file.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Feb 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vp93-v8xp-q5r9

## What is CVE-2010-4740?

CVE-2010-4740 is a critical memory corruption vulnerability in n/a, published on 16 Feb 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Stack-based buffer overflow in WTclient.dll in SCADA Engine BACnet OPC Client before 1.0.25 allows user-assisted remote attackers to execute arbitrary code via a crafted .csv file, related to a status log message.

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

## Which versions are affected by CVE-2010-4740?

It affects 1 product.


Products: Scadaengine Bacnet Opc Client.

## How do I fix CVE-2010-4740?

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

## Is CVE-2010-4740 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-4740 exists.

Public exploit code:

- BACnet OPC Client - Local Buffer Overflow (1) (exploitdb)
- BACnet OPC Client Buffer Overflow (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-4740 and fix it if it is affected.

What it is: CVE-2010-4740 is a critical memory corruption vulnerability in n/a, published on 16 Feb 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-4740 exists.

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-2010-4740/ (Markdown: https://insights.sbomify.com/CVE-2010-4740/index.md)
```

## Sources

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

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