dbcve.org
Business IntelligenceApplication · Oracle

CVE-2023-21965

MEDIUM · 5.7 CVSS v3.1 Published 2023-04-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

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 Business Intelligence Enterprise Edition product of Oracle Analytics (component: Analytics Server). The supported version that is affected is 6.4.0.0.0. Easily exploitable vulnerability allows low privileged 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. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Business Intelligence Enterprise Edition accessible data. CVSS 3.1 Base Score 5.7 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 · moderate confidence

An injection vulnerability in Oracle Business Intelligence Enterprise Edition 6.4.0.0.0 Analytics Server allows low-privileged attackers with network access via HTTP and user interaction to execute unauthorized access to sensitive data.

MitigationApply Oracle's security patch for this vulnerability; as a temporary measure, restrict network access to the Analytics Server and implement input validation. CVSS indicates user interaction required, suggesting this may be a reflected XSS or similar injection flaw.

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
Business IntelligenceApplication
Affected:= 6.4.0.0.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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 Oracle BI EE installation
    Check for Oracle Business Intelligence Enterprise Edition installation by inspecting the Oracle BI Home directory, commonly found at $ORACLE_HOME/bi or C:\Oracle\Middleware\bi\bitools\bin, or look for 'Oracle Business Intelligence' in installed programs on Windows
    Affected if Oracle Business Intelligence Enterprise Edition is not installed, then not affected
  2. Verify Analytics Server version
    Locate the version file or check the Analytics Server console. The version is typically displayed in the Analytics console (Fusion Middleware Control) or can be checked via the opmnctl command: cd $ORACLE_HOME/bin && ./opmnctl status -l or check the About page in Fusion Middleware Control
    Affected if Version is exactly 6.4.0.0.0 - other versions are not affected by this specific CVE
  3. Confirm Analytics Server is running and exposed
    Check if the Analytics Server process (coreapplication_obiccs1) is running using opmnctl status and verify HTTP listeners are active. Also check if the Analytics endpoint is accessible over network on ports 9500-9502 or 9704-9706 commonly used
    Affected if Analytics Server is running and exposed via HTTP network access, creating the attack surface
  4. Check for external network exposure
    Review firewall rules, load balancer configurations, and network ACLs to determine if the Analytics Server HTTP ports are accessible from untrusted networks. Check web server configuration files (instanceconfig.xml, mod_weblogic.conf) for listener bindings
    Affected if Analytics Server HTTP endpoint is reachable from outside the trusted network without proper access controls

Affected only if Oracle BI Enterprise Edition version 6.4.0.0.0 is installed AND the Analytics Server component is running and network-accessible via HTTP.

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 Oracle's security patch for this vulnerability; as a temporary measure, restrict network access to the Analytics Server and implement input validation. CVSS indicates user interaction required, suggesting this may be a reflected XSS or similar injection flaw.

Fix this in Business Intelligence Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-21965 — 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-2023-21965 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