# CVE-2012-5444: Missing authorization in n/a

> Remote attackers can create unauthorized conferences on Cisco VCS due to improper search rule processing, requiring vendor patches.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g392-qjx3-m63p

## What is CVE-2012-5444?

CVE-2012-5444 is a medium-severity missing authorization vulnerability in n/a, published on 17 Jan 2013. It can be exploited over the network, with no action from the victim.

### Official description

Cisco TelePresence Video Communication Server (VCS) X7.0.3 does not properly process certain search rules, which allows remote attackers to create conferences via an unspecified Conductor request, aka Bug ID CSCub67989.

Weakness: CWE-264

## Which versions are affected by CVE-2012-5444?

It affects 1 product.


Products: Cisco Telepresence Video Communication Servers Software.

## How do I fix CVE-2012-5444?

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

## Is CVE-2012-5444 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5444 and fix it if it is affected.

What it is: CVE-2012-5444 is a medium-severity missing authorization vulnerability in n/a, published on 17 Jan 2013. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-5444 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-2012-5444/ (Markdown: https://insights.sbomify.com/CVE-2012-5444/index.md)
```

## Sources

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

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