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

> Remote attackers can execute arbitrary code on IGSS SCADA systems by sending a crafted packet to TCP port 20222, triggering memory corruption.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** Not needed
- **Fix available:** No
- **Published:** 31 May 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8hch-7jrh-5gj5

## What is CVE-2011-2214?

CVE-2011-2214 is a critical memory corruption vulnerability in n/a, published on 31 May 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in the Open Database Connectivity (ODBC) component in 7T Interactive Graphical SCADA System (IGSS) before 9.0.0.11143 allows remote attackers to execute arbitrary code via a crafted packet to TCP port 20222, which triggers memory corruption related to an "invalid structure being used."

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

It affects 1 product.


Products: 7t Igss.

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

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

## Is CVE-2011-2214 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-2959](https://insights.sbomify.com/CVE-2011-2959/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-1565](https://insights.sbomify.com/CVE-2011-1565/): Path traversal in n/a (critical 10.0)
- [CVE-2011-1566](https://insights.sbomify.com/CVE-2011-1566/): Path traversal in n/a (critical 10.0)
- [CVE-2011-1567](https://insights.sbomify.com/CVE-2011-1567/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-1568](https://insights.sbomify.com/CVE-2011-1568/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2214 is a critical memory corruption vulnerability in n/a, published on 31 May 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-2214 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-2214/ (Markdown: https://insights.sbomify.com/CVE-2011-2214/index.md)
```

## Sources

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

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