dbcve.org
Communications Operations MonitorApplication · Oracle

CVE-2022-21401

MEDIUM · 6.6 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 →
72/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
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. While the vulnerability is in Oracle Communications Operations Monitor, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Communications Operations Monitor accessible data as well as unauthorized read access to a subset of Oracle Communications Operations Monitor accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Communications Operations Monitor. CVSS 3.1 Base Score 6.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L).

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

Vulnerability in Oracle Communications Operations Monitor's Mediation Engine allows high-privileged attackers with network access via HTTP to perform unauthorized read, insert, update, and delete operations on a subset of accessible data, plus cause partial denial of service. The attack may also significantly impact additional products due to scope change.

MitigationApply Oracle's security patch for this vulnerability (contact Oracle Support for patch availability). Until patch is applied, strictly limit network access to high-privileged accounts and minimize exposure of the Mediation Engine component.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 product installation directory or check for running processes related to Oracle Communications Operations Monitor. Common paths include /opt/oracle/ocom or check for processes named 'ocom', 'opsmonitor', or 'mediation'
    Affected if The product Oracle Communications Operations Monitor is installed
  2. Determine installed version
    Check the product version using Oracle command-line utilities, admin web interface, or version file in the installation directory. Common locations: $ORACLE_HOME/ocom/version or via 'opmnctl status' command
    Affected if The installed version equals 3.4, 4.2, 4.3, 4.4, or 5.0
  3. Verify Mediation Engine component is present
    Confirm the Mediation Engine component is installed and enabled. Check Oracle Process Manager (OPMN) configuration or Mediation Engine-specific processes are running. Look for configuration files in the mediation engine directory
    Affected if Mediation Engine component is installed and running
  4. Assess network exposure of Mediation Engine
    Review network configuration to determine if Mediation Engine HTTP interfaces are accessible from untrusted networks. Check firewall rules, load balancer configurations, and access control lists restricting HTTP access to the Mediation Engine
    Affected if Mediation Engine HTTP interface is accessible from untrusted network segments

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 exposed to network access, the environment is affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's security patch for this vulnerability (contact Oracle Support for patch availability). Until patch is applied, strictly limit network access to high-privileged accounts and minimize exposure of the Mediation Engine component.

Fix this in Communications Operations Monitor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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