dbcve.org
Communications Billing And Revenue ManagementApplication · Oracle

CVE-2022-21266

HIGH · 7.5 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 →
84/100
Remediation priority · High
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: Pipeline 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. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Communications Billing and Revenue Management accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

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 vulnerability in Oracle Communications Billing and Revenue Management's Pipeline Manager component allows remote attackers via HTTP to access sensitive data without credentials. The CVSS 3.1 score of 7.5 reflects high confidentiality impact from network-exploitable attacks requiring no authentication or user interaction.

MitigationApply the relevant Oracle security patch for this vulnerability in version 12.0.0.3 or 12.0.0.4. Consider network segmentation and WAF rules as compensating controls until the patch can be deployed.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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
    Run the version check command for your Oracle Communications Billing and Revenue Management installation. Typically this can be done via the pinVersion utility or by querying the CM (Connection Manager) with: pinctls CM -version or checking the installation logs. Alternatively, check the $PIN_HOME/etc/pin.conf file or the Oracle inventory for the installed version string.
    Affected if The installed version matches exactly 12.0.0.3.0 or 12.0.0.4.0
  2. Confirm Pipeline Manager component is in use
    Verify that the Pipeline Manager module is installed and active in your environment. Check for the presence of Pipeline Manager processes (such as pipeline or related executables in the installation directory) or review the configuration files under the Pipeline Manager configuration directory.
    Affected if Pipeline Manager component is installed and running in your environment
  3. Verify HTTP exposure of Pipeline Manager
    Check the Pipeline Manager network configuration to determine if HTTP listeners are enabled. Review the Pipeline Manager configuration files (typically in the config/ directory) for HTTP or web service endpoint settings. Also verify if the Pipeline Manager port is exposed to network access rather than being restricted to localhost.
    Affected if Pipeline Manager is accessible via HTTP on a network-exposed port

You are affected if your Oracle Communications Billing and Revenue Management installation is exactly version 12.0.0.3.0 or 12.0.0.4.0 AND the Pipeline Manager component is running and accessible via HTTP on a network-accessible interface.

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 the relevant Oracle security patch for this vulnerability in version 12.0.0.3 or 12.0.0.4. Consider network segmentation and WAF rules as compensating controls until the patch can be deployed.

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-21266 — 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-21266 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