dbcve.org
Communications Billing And Revenue ManagementApplication · Oracle

CVE-2022-21275

CRITICAL · 10.0 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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Billing and Revenue Management product of Oracle Communications Applications (component: Connection Manager). Supported versions that are affected are 12.0.0.3 and 12.0.0.4. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Communications Billing and Revenue Management. While the vulnerability is in Oracle Communications Billing and Revenue Management, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Oracle Communications Billing and Revenue Management. CVSS 3.1 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 · high confidence

Critical unauthenticated remote code execution vulnerability in Oracle Communications Billing and Revenue Management's Connection Manager component (versions 12.0.0.3-12.0.0.4). The flaw allows unauthenticated attackers with network access via HTTP to achieve complete system takeover with no user interaction required.

MitigationApply Oracle Critical Patch Update (CPU) patches for January 2022 or later. If patches unavailable, restrict network access to Connection Manager ports and implement web application firewall protections as compensating controls.

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 Billing And Revenue ManagementApplication
Affected:= 12.0.0.3.0= 12.0.0.4.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
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 if Oracle Communications Billing and Revenue Management is installed
    Locate the Oracle CBBRM installation directory or check for related processes and services on the system. Common installation paths include $ORACLE_HOME/brm or similar. Look for processes named 'CM' or 'Connection Manager' in running process lists.
    Affected if The software is not present, the check is not applicable. If present, proceed to version check.
  2. Determine the installed version of Oracle Communications Billing and Revenue Management
    Check the version of the installed Oracle CBBRM software. This is typically found in the product's About or version file, or can be queried via the system's package manager or Oracle inventory. Compare your installed version against the affected versions 12.0.0.3.0 and 12.0.0.4.0.
    Affected if Your installed version exactly matches 12.0.0.3.0 or 12.0.0.4.0, indicating you are running a vulnerable version.
  3. Verify if the Connection Manager component is enabled and running
    Check whether the Connection Manager (CM) component of Oracle CBBRM is enabled and actively running. This can be done by checking for CM-related processes, services, or by querying the system's service management utility.
    Affected if Connection Manager is not installed, disabled, or not running, the vulnerability may not be exploitable in your environment.
  4. Check network exposure of Connection Manager ports
    Identify which ports the Connection Manager is configured to listen on (typically ports in the 5000-6000 range or as configured in your environment). Use network scanning tools or check listening ports on the system. Determine if these ports are accessible from untrusted networks.
    Affected if Connection Manager ports are exposed to untrusted network access (e.g., directly accessible via the internet or from non-trusted internal networks), increasing the risk of exploitation.

You are affected if Oracle Communications Billing and Revenue Management version 12.0.0.3.0 or 12.0.0.4.0 is installed with Connection Manager enabled and exposed to network access.

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 Critical Patch Update (CPU) patches for January 2022 or later. If patches unavailable, restrict network access to Connection Manager ports and implement web application firewall protections as compensating controls.

Fix this in Communications Billing And Revenue Management Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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