Security readout for executives and security teams
Plain-English summary
CVE-2022-21572 affects Oracle Communications Billing and Revenue Management Billing Care versions 12.0.0.4.0 through 12.0.0.6.0. A low-privileged user with HTTP access could, with another user’s interaction, read or modify some billing data. The impact is data confidentiality and integrity, not service outage.
Executive priority
Treat as a scheduled but important remediation item for organizations using Oracle BRM Billing Care. The business concern is unauthorized billing data access or modification, with no source evidence of active exploitation or availability impact.
Technical view
The issue is in Oracle Communications Billing and Revenue Management, component Billing Care. Oracle lists CVSS 3.1 score 5.4 with AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. Scope change is noted, meaning successful exploitation may affect additional products beyond the vulnerable BRM component.
Likely exposure
Exposure is most likely where affected Billing Care versions are reachable over HTTP by low-privileged authenticated users. Internet exposure is not stated in the sources, so confirm actual network placement and access paths.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation. Exploitation requires low privileges, network access over HTTP, and human interaction from someone other than the attacker.
Researcher notes
Sources do not identify a CWE, detailed root cause, exploit technique, or fixed version. Analysis should stay bounded to Oracle’s published description, CVSS vector, affected versions, and the July 2022 Critical Patch Update reference.
Mitigation direction
- Review Oracle July 2022 CPU guidance for remediation details.
- Apply Oracle-supported updates or fixes for affected BRM versions.
- Restrict Billing Care HTTP access to trusted users and networks.
- Review low-privileged accounts with Billing Care access.
- Monitor billing data changes for unusual reads or modifications.
Validation and detection
- Inventory Oracle BRM Billing Care deployments and versions.
- Confirm whether versions 12.0.0.4.0 through 12.0.0.6.0 are present.
- Verify Billing Care HTTP exposure and authentication boundaries.
- Check whether Oracle July 2022 CPU remediation is applied.
- Review logs for suspicious read, insert, update, or delete activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2022-21572 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N2.32.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.oracle.com/security-alerts/cpujul2022.htmlCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
