# CVE-2010-1570: Denial of service in n/a

> Remote attackers can cause denial of service in Cisco UCCX CTI server by sending malformed messages, affecting availability.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 10 Jun 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cjjr-c6mv-9759

## What is CVE-2010-1570?

CVE-2010-1570 is a high-severity denial of service vulnerability in n/a, published on 10 Jun 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The computer telephony integration (CTI) server component in Cisco Unified Contact Center Express (UCCX) 7.0 before 7.0(1)SR4 and 7.0(2), 6.0 before 6.0(1)SR1, and 5.0 before 5.0(2)SR3 allows remote attackers to cause a denial of service (CTI server and Node Manager failure) via a malformed CTI message.

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

It affects 3 products.


Products: Cisco Customer Response Solution, Cisco Unified Contact Center Express, Cisco Unified Ip Interactive Voice Response.

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

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

## Is CVE-2010-1570 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-1571](https://insights.sbomify.com/CVE-2010-1571/): Path traversal in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-1570 is a high-severity denial of service vulnerability in n/a, published on 10 Jun 2010. 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-2010-1570 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-1570/ (Markdown: https://insights.sbomify.com/CVE-2010-1570/index.md)
```

## Sources

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

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