CVE-2022-21419
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 Business Intelligence Enterprise Edition product of Oracle Fusion Middleware (component: Visual Analyzer). Supported versions that are affected are 5.5.0.0.0 and 5.9.0.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Business Intelligence Enterprise Edition. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Business Intelligence Enterprise Edition, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Business Intelligence Enterprise Edition accessible data as well as unauthorized read access to a subset of Oracle Business Intelligence Enterprise Edition accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 confidenceUnauthenticated vulnerability in Oracle BI Enterprise Edition's Visual Analyzer component allows remote attackers with network access via HTTP to read and modify a subset of accessible data. The CVSS vector indicates a scope change (S:C), meaning attacks may impact additional products beyond the vulnerable component. Human interaction is required, suggesting a reflected or stored injection attack.
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= 5.5.0.0.0= 5.9.0.0.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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Oracle Business Intelligence installationLocate the Oracle BI installation directory or check for Oracle BI services running on the system. Common paths include $ORACLE_HOME/bi or C:\Oracle\BI. Check for processes named 'Oracle BI' or 'obiee' in running services.Affected if Oracle Business Intelligence is installed and running, but the version cannot be determined or is not clearly different from 5.5.0.0.0 or 5.9.0.0.0
-
Determine installed Oracle BI versionCheck the version of Oracle Business Intelligence using Oracle's standard version detection methods, such as the BI Administration Tool, opmnctl commands, or the Oracle Fusion Middleware control interface. Look for version information in the About page of Oracle BI Enterprise Edition.Affected if The installed version is exactly 5.5.0.0.0 or exactly 5.9.0.0.0
-
Verify Visual Analyzer component is enabledCheck the Oracle BI configuration to determine if the Visual Analyzer web component is enabled and accessible. This can typically be verified through the Oracle Fusion Middleware Control console or by examining the BI instance configuration files.Affected if Visual Analyzer is enabled and accessible as a web component within Oracle BI Enterprise Edition
-
Assess network exposure of Visual Analyzer endpointsIdentify network access to Visual Analyzer HTTP endpoints. Check if the BI server is directly exposed to untrusted networks or if HTTP access is available without authentication requirements. Review firewall rules and load balancer configurations controlling access to Visual Analyzer URLs.Affected if Visual Analyzer endpoints are reachable from untrusted networks without authentication or additional access controls
A user is affected if Oracle Business Intelligence version 5.5.0.0.0 or 5.9.0.0.0 is installed with Visual Analyzer enabled and accessible over the network, allowing unauthenticated remote HTTP access to Visual Analyzer data.
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 Oracle Critical Patch Update (CPU) for April 2022 that addresses CVE-2022-21419. Until patch deployment, restrict network exposure of Visual Analyzer endpoints and implement web application firewall rules.
Oracle Business Intelligence Enterprise Edition 5.5.0.0.1 or later / 5.9.0.0.1 or later (via Oracle Critical Patch Update April 2022)
- 1. Review the Oracle Critical Patch Update April 2022 for the specific patch information for CVE-2022-21419
- 2. Navigate to Oracle Support (support.oracle.com) and search for Oracle Business Intelligence Enterprise Edition security patches
- 3. Download and apply the appropriate patch for your version (5.5.0.0.0 or 5.9.0.0.0)
- 4. Test the patch in a non-production environment before applying to production
- 5. Apply the patch during a planned maintenance window
- 6. Verify the Visual Analyzer component is functioning correctly after the patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21419 — 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-21419 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