# CVE-2022-21431: Auth bypass in Communications Billing and Revenue Management

> Unauthenticated attackers can take over Oracle Communications Billing and Revenue Management via network access, leading to full system compromise.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Apr 2022
- **Updated:** 24 Sep 2024
- **Also known as:** GHSA-4xcj-gcpq-66r5

## What is CVE-2022-21431?

CVE-2022-21431 is a critical authentication bypass vulnerability in Oracle Communications Billing and Revenue Management, published on 19 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.4 and 12.0.0.5. Easily exploitable vulnerability allows unauthenticated attacker with network access via TCP 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 (scope change). 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).

## Which versions are affected by CVE-2022-21431?

It affects 1 product.


Products: Oracle Communications Billing and Revenue Management.

## How do I fix CVE-2022-21431?

No fix has been published for CVE-2022-21431 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-21431 being exploited?

There is no known exploitation of CVE-2022-21431 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Communications Billing and Revenue Management

- [CVE-2022-21275](https://insights.sbomify.com/CVE-2022-21275/): Auth bypass in Communications Billing and Revenue Management (critical 10.0)
- [CVE-2022-21389](https://insights.sbomify.com/CVE-2022-21389/): Auth bypass in Communications Billing and Revenue Management (critical 10.0)
- [CVE-2022-21390](https://insights.sbomify.com/CVE-2022-21390/): Auth bypass in Communications Billing and Revenue Management (critical 10.0)
- [CVE-2022-21276](https://insights.sbomify.com/CVE-2022-21276/): Auth bypass in Communications Billing and Revenue Management (critical 9.9)
- [CVE-2022-21391](https://insights.sbomify.com/CVE-2022-21391/): Auth bypass in Communications Billing and Revenue Management (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-21431 and fix it if it is affected.

What it is: CVE-2022-21431 is a critical authentication bypass vulnerability in Oracle Communications Billing and Revenue Management, published on 19 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-21431 in the wild and no public exploit code.

Affected product: Oracle Communications Billing and Revenue Management. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-21431/ (Markdown: https://insights.sbomify.com/CVE-2022-21431/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-21431
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-21431
- OSV: https://osv.dev/vulnerability/CVE-2022-21431

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-21431/
Summaries are generated and may contain mistakes; the official description above is the record.