# CVE-2008-6710: Privilege escalation in n/a

> Remote authenticated administrators can gain root privileges in Avaya Communication Manager via the web administration interface.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qcrj-63v9-fc2m

## What is CVE-2008-6710?

CVE-2008-6710 is a critical vulnerability in n/a, published on 10 Apr 2009. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unspecified vulnerability in the Web administration interface in Avaya Communication Manager 3.1.x before CM 3.1.4 SP2 and 4.0.x before 4.0.3 SP1 allows remote authenticated administrators to gain root privileges via unknown vectors related to "configuring data viewing or restoring credentials."

## Which versions are affected by CVE-2008-6710?

It affects 1 product.


Products: Avaya Communication Manager.

## How do I fix CVE-2008-6710?

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

## Is CVE-2008-6710 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-6708](https://insights.sbomify.com/CVE-2008-6708/): Privilege escalation in n/a (critical 9.0)
- [CVE-2008-6709](https://insights.sbomify.com/CVE-2008-6709/): Command injection in n/a (critical 9.0)
- [CVE-2008-6711](https://insights.sbomify.com/CVE-2008-6711/): Command injection in n/a (critical 9.0)
- [CVE-2008-5709](https://insights.sbomify.com/CVE-2008-5709/): Command injection in n/a (critical 9.0)
- [CVE-2008-6706](https://insights.sbomify.com/CVE-2008-6706/): Information disclosure in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6710 and fix it if it is affected.

What it is: CVE-2008-6710 is a critical vulnerability in n/a, published on 10 Apr 2009. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-6710 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-2008-6710/ (Markdown: https://insights.sbomify.com/CVE-2008-6710/index.md)
```

## Sources

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

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