dbcve.org
Communications Billing And Revenue ManagementApplication · Oracle

CVE-2022-21391

CRITICAL · 9.9 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 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 low privileged 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 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 vulnerability in Oracle Communications Billing and Revenue Management's Connection Manager component (versions 12.0.0.3 and 12.0.0.4) allows a low-privileged attacker with network access via HTTP to achieve complete system takeover, impacting confidentiality, integrity, and availability.

MitigationApply Oracle's security patch for CVE-2022-21391 immediately. Until patched, restrict network access to the Connection Manager and monitor for indicators of compromise.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm Oracle Communications Billing and Revenue Management is installed
    Check for Oracle BRM installation directories (commonly under $ORACLE_HOME or /opt/oracle) and look for the 'BillingAndRevenueManagement' or 'BRM' product directories
    Affected if The product installation directory exists on the system
  2. Identify installed BRM version
    Run 'opatch lsinventory' or check the inventory.xml file in the Oracle inventory directory, or look for version files within the BRM installation directory
    Affected if The version listed is exactly 12.0.0.3.0 or 12.0.0.4.0
  3. Verify Connection Manager component is enabled
    Check if the Connection Manager (CM) process is running: look for 'cm' or 'ConnectionManager' processes via 'ps -ef | grep -i cm' and check for CM-related configuration files in the BRM home directory
    Affected if The Connection Manager component is installed and running
  4. Check network exposure of Connection Manager
    Identify the CM port (typically 11999 or as configured in CM configuration files) and verify listening status via 'netstat -an | grep <port>' or 'ss -tlnp | grep <port>'; check if the port is bound to a non-localhost interface
    Affected if The CM port is listening on a reachable network interface (not 127.0.0.1 only)
  5. Assess attacker accessibility
    Review firewall rules and network ACLs to determine if HTTP access to the CM port is permitted from untrusted networks, and verify whether the CM supports HTTP protocol
    Affected if The CM port is accessible from network segments beyond localhost or trusted admin networks

The environment is affected if Oracle Communications Billing and Revenue Management version 12.0.0.3.0 or 12.0.0.4.0 is installed with the Connection Manager component 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's security patch for CVE-2022-21391 immediately. Until patched, restrict network access to the Connection Manager and monitor for indicators of compromise.

Fix this in Communications Billing And Revenue Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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