dbcve.org
Communications Billing And Revenue ManagementApplication · Oracle

CVE-2022-21389

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

An unauthenticated remote code execution vulnerability in the Connection Manager component of Oracle Communications Billing and Revenue Management versions 12.0.0.3 and 12.0.0.4 allows attackers with network access via HTTP to completely compromise the system, achieving full takeover with impact to confidentiality, integrity, and availability.

MitigationApply Oracle's security patches for this vulnerability or upgrade to a supported version; implement network segmentation or web application firewall controls to restrict unauthorized HTTP access to the Connection Manager until the patch can be applied.

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 BRM installation directories or check for processes related to billing and revenue management software. Common installation paths include $ORACLE_HOME/brm or check running services for BRM components.
    Affected if The product is installed and running on the system
  2. Verify the exact BRM version
    Use Oracle utility commands such as 'opatch lsinventory' or check version files in the BRM installation directory. The exact version string must match 12.0.0.3.0 or 12.0.0.4.0.
    Affected if Installed version equals 12.0.0.3.0 or 12.0.0.4.0 exactly
  3. Confirm the Connection Manager component is exposed
    Check if the Connection Manager (CM) web interface is listening on HTTP ports. Review network configuration for exposed HTTP listeners typically on ports 8080, 8443, or configured custom ports.
    Affected if Connection Manager is accessible via HTTP network access
  4. Check if network access is unauthenticated
    Review access controls, firewall rules, and web application configuration to determine if the Connection Manager HTTP endpoints accept requests without authentication.
    Affected if HTTP access to Connection Manager does not require authentication

If Oracle Communications Billing and Revenue Management version 12.0.0.3.0 or 12.0.0.4.0 is installed with its Connection Manager exposed to unauthenticated HTTP network access, the system is vulnerable to CVE-2022-21389.

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 security patches for this vulnerability or upgrade to a supported version; implement network segmentation or web application firewall controls to restrict unauthorized HTTP access to the Connection Manager until the patch can be applied.

Recommended fix Moderate confidence

Oracle Communications Billing and Revenue Management 12.0.0.5 or later (or apply Jan 2022 Critical Patch Update)

  1. Check Oracle Critical Patch Update advisories for January 2022 or later for CVE-2022-21389
  2. Obtain the applicable patch from Oracle Support (patch numbers vary by version)
  3. Apply the patch following Oracle's standard patch application procedures for Communications Billing and Revenue Management
  4. Verify the patch was applied successfully by checking the Connection Manager component version
  5. Test that the Connection Manager accepts legitimate traffic after patching
  6. Confirm no unauthorized access or changes to the system
Caveat Review Oracle's patch readme for any known issues or configuration changes required for this specific patch

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

Fix this in Communications Billing And Revenue Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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