dbcve.org
Contrail Service OrchestrationApplication · Juniper

CVE-2022-22189

HIGH · 7.8 CVSS v3.1 Published 2022-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
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.

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

This is an Incorrect Ownership Assignment vulnerability in Juniper Contrail Service Orchestration 6.0.0 that allows a locally authenticated user to elevate privileges without additional authentication, effectively achieving local root/administrative control over the system they are already logged into.

MitigationApply Juniper Contrail Service Orchestration 6.0.0 Patch v3 or later to remediate the incorrect ownership assignment. Prior to patching, limit local system access to trusted personnel only.

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

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify installed Contrail Service Orchestration version
    Run the command to display the Contrail Service Orchestration version (e.g., contrail-version, rpm query, or web UI version display)
    Affected if The installed version is exactly 6.0.0 (matches the affected version range)
  2. Confirm the specific vulnerable release
    Cross-reference the version output to ensure it is the 6.0.0 release and not a later patch version
    Affected if The version string shows 6.0.0 without any patch level indicator (e.g., no v3 or later suffix)
  3. Verify local user access exists
    Check for existing local user accounts on the system with shell or console access
    Affected if Local authenticated users are present who could attempt privilege escalation

A system is affected if Juniper Contrail Service Orchestration version 6.0.0 is installed without the v3 or later patch applied.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Juniper Contrail Service Orchestration 6.0.0 Patch v3 or later to remediate the incorrect ownership assignment. Prior to patching, limit local system access to trusted personnel only.

Recommended fix Moderate confidence

6.0.0 Patch v3 or later

  1. 1. Backup the current Contrail Service Orchestration configuration and database before applying any updates.
  2. 2. Verify the current installed version of Contrail Service Orchestration using the administrative interface or command-line tools.
  3. 3. Download Contrail Service Orchestration version 6.0.0 Patch v3 or later from the Juniper Networks support portal at kb.juniper.net.
  4. 4. Review the patch release notes and installation instructions provided by Juniper Networks.
  5. 5. Apply the patch following the documented upgrade procedure for Contrail Service Orchestration on-premises installations.
  6. 6. Verify the patch was applied successfully by checking the software version.
  7. 7. Test that the authentication and permission escalation vulnerability is resolved and system functionality is intact.

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

Fix this in Contrail Service Orchestration Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22189 — 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-22189 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