CVE-2022-21429
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 · uneditedVulnerability in the Oracle Communications Billing and Revenue Management product of Oracle Communications Applications (component: Billing Care). Supported versions that are affected are 12.0.0.4.0-12.0.0.6.0. Difficult to exploit 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 takeover of Oracle Communications Billing and Revenue Management. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/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 confidenceThis is an unauthenticated remote code execution vulnerability in the Billing Care component of Oracle Communications Billing and Revenue Management. An attacker with network access via HTTP can exploit this flaw to achieve complete system takeover without any credentials. The CVSS vector indicates high attack complexity, but the impact is total compromise of confidentiality, integrity, and availability.
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>= 12.0.0.4.0, <= 12.0.0.6.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Billing Care component is installedLocate Oracle Communications Billing and Revenue Management installation directories and check for the Billing Care web application component (commonly in a 'billingcare' or 'portal' subdirectory under the Oracle BRM installation path)Affected if The Billing Care web application directory exists on the system
-
Determine the installed Billing Care versionCheck version information in the Billing Care installation - typically found in manifest files, version.properties, or the billing care WAR/ear file metadata within the installation directoryAffected if The installed version falls within the range 12.0.0.4.0 through 12.0.0.6.0 inclusive
-
Verify the HTTP listener is enabledCheck the Billing Care configuration files (such as web.xml or application configuration) to confirm the HTTP servlet/endpoint is actively enabled and configured to accept requestsAffected if The Billing Care HTTP interface is enabled and listening for connections
-
Confirm network accessibility of Billing CareTest network connectivity to the Billing Care HTTP port (commonly ports 8080, 8000, or configured custom ports) from untrusted networks using curl, telnet, or port scanning toolsAffected if The Billing Care HTTP endpoint is reachable from network segments that are not restricted to trusted sources only
A system is affected if Oracle Communications Billing and Revenue Management with Billing Care version 12.0.0.4.0 through 12.0.0.6.0 is installed and its HTTP interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the Oracle Critical Patch Update that addresses CVE-2022-21429 to upgrade Billing Care to a supported version. If immediate patching is not possible, restrict network access to the Billing Care HTTP interface to trusted sources only.
12.0.0.7.0 or later
- Identify the current Oracle Communications Billing and Revenue Management version using the billing admin console or command line tools.
- Review the Oracle Communications Billing and Revenue Management 12.0.0.7.0 release notes and upgrade documentation for Billing Care component.
- Plan maintenance window as upgrade requires system downtime.
- Back up current configuration, database, and installation files.
- Stop all Oracle BRM services including Billing Care.
- Upgrade to version 12.0.0.7.0 or later using Oracle's upgrade utilities following the documented migration path.
- After upgrade, verify Billing Care component is operational.
- Validate system functionality and confirm vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21429 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-21429 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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