dbcve.org
Communications Billing And Revenue ManagementApplication · Oracle

CVE-2022-21390

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: Webservices 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

Unauthenticated HTTP-based vulnerability in the Webservices Manager component of Oracle Communications Billing and Revenue Management versions 12.0.0.3 and 12.0.0.4 allows remote attackers with network access to achieve complete system takeover, impacting confidentiality, integrity, and availability.

MitigationApply Oracle Critical Patch Update or upgrade to a patched version; until then, restrict network access to the Webservices Manager HTTP interface.

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 installed Oracle BRM version
    Query the BRM system or check the installation directory for the exact version number of Oracle Communications Billing and Revenue Management. Common locations include the installation logs, opmn.xml, or the CM (Connection Manager) configuration files.
    Affected if The installed version is exactly 12.0.0.3.0 or 12.0.0.4.0
  2. Locate Webservices Manager component
    Identify whether the Webservices Manager module is installed and configured in the BRM environment. Check the BRM home directory for webservices or wsmanager related directories and configuration files.
    Affected if Webservices Manager component is present in the installation
  3. Verify Webservices Manager HTTP interface status
    Determine if the Webservices Manager HTTP listener is enabled and running. Check the Oracle Process Manager and Notification Server (OPMN) configuration or the Webservices Manager configuration files for HTTP port bindings and service status.
    Affected if The Webservices Manager HTTP interface is enabled and actively listening on a network port
  4. Test network accessibility of Webservices Manager
    From a remote host, attempt to access the Webservices Manager HTTP endpoint using the configured port (commonly ports in the 80xx or 8080 range for BRM Webservices). Use a tool like curl or telnet to check if the port responds to HTTP requests.
    Affected if The Webservices Manager HTTP port is accessible from untrusted network segments or the internet

Affected if the installed BRM version is exactly 12.0.0.3.0 or 12.0.0.4.0 AND the Webservices Manager HTTP interface is enabled and 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 Oracle Critical Patch Update or upgrade to a patched version; until then, restrict network access to the Webservices Manager HTTP interface.

Recommended fix High confidence

Oracle Communications Billing and Revenue Management 12.0.0.5 or later

  1. 1. Download Oracle Communications Billing and Revenue Management version 12.0.0.5 or later from Oracle eDelivery (edelivery.oracle.com)
  2. 2. Review the Oracle BRM Installation Guide for upgrade procedures
  3. 3. Backup the existing Oracle BRM database and configuration files
  4. 4. Stop all Oracle BRM services including CM, DM, and Webservices Manager
  5. 5. Run the Oracle BRM upgrade installer following the official upgrade documentation
  6. 6. Verify the Webservices Manager component is properly configured after upgrade
  7. 7. Start all Oracle BRM services and verify the application is functioning correctly
  8. 8. Perform security validation to confirm the vulnerability is remediated
Caveat Upgrade may require downtime and should be tested in a non-production environment first; review Oracle upgrade documentation for any configuration migration requirements

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
  • 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-21390 — 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-21390 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