# CVE-2022-22189: Privilege escalation in Contrail Service Orchestration

> An authenticated local user can elevate permissions and take control of the system via the management interface without further authentication.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Apr 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mr95-wr78-6g74

## What is CVE-2022-22189?

CVE-2022-22189 is a high-severity vulnerability in Juniper Networks Contrail Service Orchestration, published on 14 Apr 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An Incorrect Ownership Assignment vulnerability in Juniper Networks Contrail Service Orchestration (CSO) allows a locally authenticated user to have their permissions elevated without authentication thereby taking control of the local system they are currently authenticated to. This issue affects: Juniper Networks Contrail Service Orchestration 6.0.0 versions prior to 6.0.0 Patch v3 on On-premises installations. This issue does not affect Juniper Networks Contrail Service Orchestration On-premises versions prior to 6.0.0.

Weakness: CWE-708 (Incorrect Ownership Assignment), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2022-22189?

It affects 1 product.


Products: Juniper Contrail Service Orchestration.

## How do I fix CVE-2022-22189?

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

## Is CVE-2022-22189 being exploited?

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

## Other vulnerabilities in Juniper Networks Contrail Service Orchestration

- [CVE-2018-0038](https://insights.sbomify.com/CVE-2018-0038/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2018-0040](https://insights.sbomify.com/CVE-2018-0040/): Contrail Service Orchestration: hardcoded cryptographic certificates and keys (critical 9.8)
- [CVE-2018-0041](https://insights.sbomify.com/CVE-2018-0041/): Contrail Service Orchestration: Hardcoded credentials for Keystone service. (critical 9.8)
- [CVE-2018-0042](https://insights.sbomify.com/CVE-2018-0042/): Juniper Networks CSO versions prior to 4.0.0 may log passwords in log files leading to an information disclosure vulnerability. (critical 9.8)
- [CVE-2022-22152](https://insights.sbomify.com/CVE-2022-22152/): Contrail Service Orchestration: Tenants able to see other tenants policies via REST API interface (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22189 and fix it if it is affected.

What it is: CVE-2022-22189 is a high-severity vulnerability in Juniper Networks Contrail Service Orchestration, published on 14 Apr 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-22189 in the wild and no public exploit code.

Affected product: Juniper Networks Contrail Service Orchestration. 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-2022-22189/ (Markdown: https://insights.sbomify.com/CVE-2022-22189/index.md)
```

## Sources

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

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