# CVE-2018-0322: Missing authorization in Cisco Prime Collaboration Provisioning unknown

> Authenticated attackers can modify sensitive data of higher-privileged accounts due to missing access restrictions in Cisco Prime Collaboration Provisioning.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 7 Jun 2018
- **Updated:** 29 Nov 2024
- **Also known as:** GHSA-445v-c68q-3683

## What is CVE-2018-0322?

CVE-2018-0322 is a high-severity missing authorization vulnerability in Cisco Prime Collaboration Provisioning unknown, published on 7 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the web management interface of Cisco Prime Collaboration Provisioning (PCP) could allow an authenticated, remote attacker to modify sensitive data that is associated with arbitrary accounts on an affected device. The vulnerability is due to a failure to enforce access restrictions on the Help Desk and User Provisioning roles that are assigned to authenticated users. This failure could allow an authenticated attacker to modify critical attributes of higher-privileged accounts on the device. A successful exploit could allow the attacker to gain elevated privileges on the device. This vulnerability affects Cisco Prime Collaboration Provisioning (PCP) Releases 12.1 and prior. Cisco Bug IDs: CSCvd61779.

Weakness: CWE-862 (Missing Authorization), CWE-264

## Which versions are affected by CVE-2018-0322?

It affects 2 products.


Products: Cisco Prime Collaboration, Cisco Prime Collaboration Provisioning.

## How do I fix CVE-2018-0322?

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

## Is CVE-2018-0322 being exploited?

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

## Other vulnerabilities in Cisco Prime Collaboration Provisioning unknown

- [CVE-2018-15389](https://insights.sbomify.com/CVE-2018-15389/): Cisco Prime Collaboration Provisioning Intermittent Hard-Coded Password Vulnerability (critical 9.8)
- [CVE-2018-0318](https://insights.sbomify.com/CVE-2018-0318/): Auth bypass in Cisco Prime Collaboration Provisioning unknown (critical 9.8)
- [CVE-2018-0319](https://insights.sbomify.com/CVE-2018-0319/): Auth bypass in Cisco Prime Collaboration Provisioning unknown (critical 9.8)
- [CVE-2018-0320](https://insights.sbomify.com/CVE-2018-0320/): SQL injection in Cisco Prime Collaboration Provisioning unknown (critical 9.8)
- [CVE-2018-0321](https://insights.sbomify.com/CVE-2018-0321/): Auth bypass in Cisco Prime Collaboration Provisioning unknown (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0322 and fix it if it is affected.

What it is: CVE-2018-0322 is a high-severity missing authorization vulnerability in Cisco Prime Collaboration Provisioning unknown, published on 7 Jun 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-0322 in the wild and no public exploit code.

Affected product: Cisco Prime Collaboration Provisioning unknown. 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-2018-0322/ (Markdown: https://insights.sbomify.com/CVE-2018-0322/index.md)
```

## Sources

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

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