dbcve.org
Communications Operations MonitorApplication · Oracle

CVE-2022-21395

HIGH · 7.2 CVSS v3.1 Published 2022-01-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Vulnerability in the Oracle Communications Operations Monitor product of Oracle Communications (component: Mediation Engine). Supported versions that are affected are 3.4, 4.2, 4.3, 4.4 and 5.0. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Communications Operations Monitor. Successful attacks of this vulnerability can result in takeover of Oracle Communications Operations Monitor. CVSS 3.1 Base Score 7.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).

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 · moderate confidence

This is a vulnerability in Oracle Communications Operations Monitor's Mediation Engine component. It allows a high-privileged attacker with network access via HTTP to achieve full system takeover, impacting confidentiality, integrity, and availability equally. The vulnerability is easily exploitable and affects versions 3.4, 4.2, 4.3, 4.4, and 5.0.

MitigationApply the Oracle security patch for CVE-2022-21395 to the affected Oracle Communications Operations Monitor installation. Until the patch is available, restrict network access to the Mediation Engine to trusted administrative users 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
Communications Operations MonitorApplication
Affected:= 3.4= 4.2= 4.3= 4.4= 5.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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 Oracle Communications Operations Monitor installation
    Locate the Oracle Communications Operations Monitor installation directory and locate its version information file or use the product's version command-line tool if available
    Affected if The product is not installed, the vulnerability does not apply
  2. Verify the installed version against affected releases
    Compare your installed version to the list of affected versions: 3.4, 4.2, 4.3, 4.4, and 5.0
    Affected if The installed version exactly matches 3.4, 4.2, 4.3, 4.4, or 5.0
  3. Confirm Mediation Engine component is present
    Check if the Mediation Engine component is installed and enabled within the Oracle Communications Operations Monitor deployment
    Affected if Mediation Engine is not present, the specific flaw does not apply
  4. Check network exposure of Mediation Engine HTTP interface
    Determine if the Mediation Engine HTTP management or API interface is accessible over the network from untrusted sources
    Affected if The Mediation Engine HTTP interface is exposed to untrusted network access, the vulnerability is exploitable remotely

Your environment is affected if Oracle Communications Operations Monitor version 3.4, 4.2, 4.3, 4.4, or 5.0 is installed with the Mediation Engine component enabled and its HTTP interface is network-accessible.

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 the Oracle security patch for CVE-2022-21395 to the affected Oracle Communications Operations Monitor installation. Until the patch is available, restrict network access to the Mediation Engine to trusted administrative users only.

Recommended fix Moderate confidence

Apply Oracle Critical Patch Update (CPU) for January 2022 or later; contact Oracle for specific version number

  1. 1. Navigate to Oracle Support (support.oracle.com) and search for CVE-2022-21395 or the Oracle Communications Operations Monitor patch.
  2. 2. Download the applicable security patch for your specific version (3.4, 4.2, 4.3, 4.4, or 5.0).
  3. 3. Review the patch readme for pre-installation requirements and prerequisites.
  4. 4. Back up the current Oracle Communications Operations Monitor installation and database.
  5. 5. Apply the patch following the instructions in the patch documentation.
  6. 6. Verify the patch was applied successfully by checking the product version and confirming all Mediation Engine components are operational.
  7. 7. Test critical workflows to ensure the patched system functions correctly.

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

Fix this in Communications Operations Monitor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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