# CVE-2022-22152: Contrail Service Orchestration: Tenants able to see other tenants policies via REST API interface

> Tenants can view other tenants' confidential firewall and access control policies via the REST API, exposing sensitive configuration data.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **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:** 19 Jan 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hv5p-2fm6-37xc

## What is CVE-2022-22152?

CVE-2022-22152 is a high-severity vulnerability in Juniper Networks Contrail Service Orchestration, published on 19 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Protection Mechanism Failure vulnerability in the REST API of Juniper Networks Contrail Service Orchestration allows one tenant on the system to view confidential configuration details of another tenant on the same system. By utilizing the REST API, one tenant is able to obtain information on another tenant's firewall configuration and access control policies, as well as other sensitive information, exposing the tenant to reduced defense against malicious attacks or exploitation via additional undetermined vulnerabilities. This issue affects Juniper Networks Contrail Service Orchestration versions prior to 6.1.0 Patch 3.

Weakness: CWE-693 (Protection Mechanism Failure)

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

It affects 1 product.


Products: Juniper Contrail Service Orchestration.

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

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

## Is CVE-2022-22152 being exploited?

There is no known exploitation of CVE-2022-22152 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-22189](https://insights.sbomify.com/CVE-2022-22189/): Privilege escalation in Contrail Service Orchestration (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22152 is a high-severity vulnerability in Juniper Networks Contrail Service Orchestration, published on 19 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22152 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-22152/ (Markdown: https://insights.sbomify.com/CVE-2022-22152/index.md)
```

## Sources

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

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