# CVE-2010-0139: SQL injection in n/a

> Remote attackers can manipulate database data via SQL injection in Cisco Unified MeetingPlace, requiring immediate patching.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:N/C:P/I:P/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2rfx-cf2v-2f6c

## What is CVE-2010-0139?

CVE-2010-0139 is a critical SQL injection vulnerability in n/a, published on 28 Jan 2010. It can be exploited over the network, with no action from the victim.

### Official description

Cisco Unified MeetingPlace 7 before 7.0(2.3) hotfix 5F, 6 before 6.0.639.2, and possibly 5 does not properly validate SQL commands, which allows remote attackers to create, modify, or delete data in a database via unspecified vectors, aka Bug ID CSCtc39691.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Cisco Unified Meetingplace.

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

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

## Is CVE-2010-0139 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-0140](https://insights.sbomify.com/CVE-2010-0140/): Missing authorization in n/a (critical 10.0)
- [CVE-2015-0702](https://insights.sbomify.com/CVE-2015-0702/): File upload in n/a (critical 9.0)
- [CVE-2010-0142](https://insights.sbomify.com/CVE-2010-0142/): Privilege escalation in n/a (high 8.5)
- [CVE-2012-5416](https://insights.sbomify.com/CVE-2012-5416/): Memory corruption in n/a (high 7.8)
- [CVE-2013-1168](https://insights.sbomify.com/CVE-2013-1168/): Auth bypass in n/a (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-0139 is a critical SQL injection vulnerability in n/a, published on 28 Jan 2010. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-0139 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-2010-0139/ (Markdown: https://insights.sbomify.com/CVE-2010-0139/index.md)
```

## Sources

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

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