# CVE-2014-3300: Missing authorization in n/a

> Remote attackers can modify user information in Cisco Unified CDM via crafted URLs due to improper access control implementation.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-433x-mwqf-j53f

## What is CVE-2014-3300?

CVE-2014-3300 is a high-severity missing authorization vulnerability in n/a, published on 7 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The BVSMWeb portal in the web framework in Cisco Unified Communications Domain Manager (CDM) in Unified CDM Application Software before 10 does not properly implement access control, which allows remote attackers to modify user information via a crafted URL, aka Bug ID CSCum77041.

Weakness: CWE-264

## Which versions are affected by CVE-2014-3300?

It affects 2 products.


Products: Cisco Unified Cdm Application Software, Cisco Unified Communications Domain Manager.

## How do I fix CVE-2014-3300?

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

## Is CVE-2014-3300 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-3300 exists.

Public exploit code:

- Viproy CUCDM IP Phone XML Services - Call Forwarding Tool (metasploit)
- Viproy CUCDM IP Phone XML Services - Speed Dial Attack Tool (metasploit)

## Other vulnerabilities in n/a

- [CVE-2014-2197](https://insights.sbomify.com/CVE-2014-2197/): Missing authorization in n/a (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3300 and fix it if it is affected.

What it is: CVE-2014-3300 is a high-severity missing authorization vulnerability in n/a, published on 7 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-3300 exists.

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-2014-3300/ (Markdown: https://insights.sbomify.com/CVE-2014-3300/index.md)
```

## Sources

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

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