dbcve.org
Contrail Service OrchestrationApplication · Juniper

CVE-2022-22152

MEDIUM · 6.5 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to after 6.0.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A tenant isolation failure in the Contrail Service Orchestration REST API allows authenticated tenants to access another tenant's confidential configuration data, including firewall rules and access control policies, due to improper authorization checks in multi-tenant API endpoints.

MitigationUpgrade to Juniper Contrail Service Orchestration 6.1.0 Patch 3 or later. As a compensating control, implement strict network segmentation and monitor API access logs for cross-tenant data access patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Contrail Service OrchestrationApplication
Affected:<= 6.0.0= 6.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Contrail Service Orchestration installation and version
    Identify the installed version of Juniper Contrail Service Orchestration in your environment. This is typically available via the product's admin interface, CLI tools, or package management system. Common methods include checking the contrail-version command output or reviewing installed package versions.
    Affected if The installed version is 6.1.0 or any version <= 6.0.0 (versions 6.1.0 and below are affected)
  2. Verify multi-tenant API endpoint exposure
    Determine whether the Contrail Service Orchestration REST API is accessible and whether multi-tenant API endpoints are enabled. Check the API service configuration and network accessibility of the REST API ports.
    Affected if Multi-tenant API endpoints are exposed and accessible to tenant users
  3. Check authorization configuration for tenant isolation
    Review the authorization and access control configuration for the multi-tenant API endpoints. Look for settings that control cross-tenant access to configuration data such as firewall rules and access control policies.
    Affected if Authorization controls allow authenticated tenants to access resources belonging to other tenants, or no explicit tenant isolation checks are configured
  4. Inspect API access logs for cross-tenant patterns
    Examine API access logs for any instances where tenant users accessed configuration data belonging to other tenants. Look for API calls that retrieve firewall rules or access control policies from different tenant contexts.
    Affected if Logs show cross-tenant data access attempts or successful retrievals of another tenant's configuration data

You are affected if Contrail Service Orchestration version 6.1.0 or lower is installed AND multi-tenant API endpoints are accessible, allowing unauthorized cross-tenant access to configuration data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 6.0.0
Interim mitigation

Upgrade to Juniper Contrail Service Orchestration 6.1.0 Patch 3 or later. As a compensating control, implement strict network segmentation and monitor API access logs for cross-tenant data access patterns.

Recommended fix High confidence

6.1.0 Patch 3 or later

  1. 1. Back up the current Contrail Service Orchestration configuration and database
  2. 2. Download Contrail Service Orchestration version 6.1.0 Patch 3 (or a later patched release) from the Juniper Networks support portal
  3. 3. Follow the standard Contrail Service Orchestration upgrade procedure as documented in the Juniper Networks administrator guide
  4. 4. After upgrade, verify that the REST API correctly enforces tenant isolation by confirming tenants cannot access other tenants' configurations
  5. 5. Validate that all services are functioning correctly post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Contrail Service Orchestration Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22152 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22152 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data