dbcve.org
Communications Operations MonitorApplication · Oracle

CVE-2022-21403

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

Vulnerability in the Mediation Engine component of Oracle Communications Operations Monitor (versions 3.4, 4.2, 4.3, 4.4, 5.0) allows high-privileged attackers with network access via HTTP to compromise the system, resulting in unauthorized read/write/delete access to some data and partial denial of service.

MitigationApply Oracle's available security patch for this vulnerability to update the affected Oracle Communications Operations Monitor installation to a patched version.

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. Confirm Oracle Communications Operations Monitor is installed
    Locate the Oracle Communications Operations Monitor installation on the system and verify the product is present
    Affected if The product is not installed or cannot be located
  2. Identify the installed version
    Use the product's version command, about page, or configuration file to determine the exact version number of the Oracle Communications Operations Monitor installation
    Affected if The installed version matches 3.4, 4.2, 4.3, 4.4, or 5.0 exactly
  3. Verify Mediation Engine component is in use
    Check the product configuration or component listing to confirm the Mediation Engine component is enabled or configured
    Affected if Mediation Engine is present and active in the configuration
  4. Assess network exposure
    Review network access controls, firewall rules, or ACLs to determine if the Mediation Engine HTTP interface is accessible from network locations
    Affected if The HTTP interface of the Mediation Engine is exposed to untrusted network access

A user 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 accessible over HTTP from untrusted networks

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 Oracle's available security patch for this vulnerability to update the affected Oracle Communications Operations Monitor installation to a patched version.

Recommended fix Moderate confidence

Oracle Communications Operations Monitor 5.0.1 or later (as per April 2022 CPU)

  1. Check the Oracle Critical Patch Update advisory for April 2022 for CVE-2022-21403
  2. Identify the specific patch number and instructions for Oracle Communications Operations Monitor from the Oracle support portal
  3. Apply the relevant quarterly critical patch update to the affected installation
  4. Verify the patch has been applied by checking the Mediation Engine component version
Caveat Review Oracle's patch documentation for any required pre-installation steps or potential compatibility considerations

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

Fix this in Communications Operations Monitor Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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