dbcve.org
Communications Billing And Revenue ManagementApplication · Oracle

CVE-2022-21424

HIGH · 8.3 CVSS v3.1 Published 2022-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
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). The supported version that is affected is 12.0.0.4. Easily exploitable vulnerability allows low privileged attacker with network access via TCP to compromise Oracle Communications Billing and Revenue Management. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Communications Billing and Revenue Management accessible data as well as unauthorized access to critical data or complete access to all Oracle Communications Billing and Revenue Management accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Communications Billing and Revenue Management. CVSS 3.1 Base Score 8.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Billing and Revenue Management Connection Manager (version 12.0.0.4) allows a low-privileged attacker with network access via TCP to achieve unauthorized creation, deletion, or modification of critical data, along with unauthorized access to critical or complete accessible data, and partial denial of service.

MitigationApply the Oracle security patch for CVE-2022-21424 or upgrade to a patched version of Oracle Communications Billing and Revenue Management.

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.4

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 installed Oracle Communications Billing and Revenue Management version
    Check the product version using Oracle inventory, product-specific version file, or cm (Connection Manager) startup logs. Typical locations include $ORACLE_HOME/inventory/ContentsXML or the cm/bin directory version info.
    Affected if The installed version is exactly 12.0.0.4
  2. Confirm exact version matches CVE
    Compare the identified version string against the affected range. This CVE affects only version 12.0.0.4 specifically, not a range.
    Affected if Version reported is 12.0.0.4 exactly
  3. Verify Connection Manager component is enabled
    Check if the Connection Manager (cm) process is running or configured to run. Look for cm process in running processes or cm configuration in the BRM home directory.
    Affected if Connection Manager is installed and enabled/running
  4. Check network exposure of Connection Manager
    Identify the TCP port configured for Connection Manager (default is 11916 or check cm configuration) and verify if the port is listening on network interfaces accessible to attackers.
    Affected if Connection Manager TCP port is accessible over network to untrusted users

Affected if Oracle Communications Billing and Revenue Management version is exactly 12.0.0.4 AND the Connection Manager component is network-accessible.

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 the Oracle security patch for CVE-2022-21424 or upgrade to a patched version of Oracle Communications Billing and Revenue Management.

Recommended fix High confidence

12.0.0.5 or later

  1. Download Oracle Communications Billing and Revenue Management version 12.0.0.5 or later from Oracle eDelivery (edelivery.oracle.com)
  2. Review the installation guide and patch readme for 12.0.0.5
  3. Backup the current database and Oracle Home directory before upgrading
  4. Stop all Oracle Communications Billing and Revenue Management services
  5. Install version 12.0.0.5 following Oracle's standard upgrade procedure
  6. Restart all services and verify the Connection Manager component is running
  7. Validate that CVE-2022-21424 is no longer exploitable by verifying the patched Connection Manager binary version

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
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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