# CVE-2006-0367: Privilege escalation in n/a

> Authenticated users with read-only privileges can escalate to full administrative access via a crafted URL in Cisco CallManager.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-frmh-p5vf-w2c9

## What is CVE-2006-0367?

CVE-2006-0367 is a medium-severity vulnerability in n/a, published on 22 Jan 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in Cisco CallManager 3.2 and earlier, 3.3 before 3.3(5)SR1, 4.0 before 4.0(2a)SR2c, and 4.1 before 4.1(3)SR2 allows remote authenticated users with read-only administrative privileges to obtain full administrative privileges via a "crafted URL on the CCMAdmin web page."

## Which versions are affected by CVE-2006-0367?

It affects 1 product.


Products: Cisco Call Manager.

## How do I fix CVE-2006-0367?

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

## Is CVE-2006-0367 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1760](https://insights.sbomify.com/CVE-2004-1760/): Auth bypass in n/a (critical 10.0)
- [CVE-2007-4634](https://insights.sbomify.com/CVE-2007-4634/): SQL injection in n/a (critical 9.3)
- [CVE-2006-0368](https://insights.sbomify.com/CVE-2006-0368/): Denial of service in n/a (high 7.8)
- [CVE-2007-5468](https://insights.sbomify.com/CVE-2007-5468/): Auth bypass in n/a (medium 5.0)
- [CVE-2005-2241](https://insights.sbomify.com/CVE-2005-2241/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0367 and fix it if it is affected.

What it is: CVE-2006-0367 is a medium-severity vulnerability in n/a, published on 22 Jan 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0367 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-2006-0367/ (Markdown: https://insights.sbomify.com/CVE-2006-0367/index.md)
```

## Sources

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

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