dbcve.org
Business IntelligenceApplication · Oracle

CVE-2023-21952

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 · high confidence

This is an information disclosure vulnerability in Oracle Business Intelligence Enterprise Edition Analytics Server version 6.4.0.0.0. A low-privileged attacker with network access via HTTP can exploit this issue, but it requires human interaction (such as a user clicking a malicious link or visiting a compromised page). The vulnerability allows unauthorized access to sensitive or confidential data due to improper access controls or path traversal in the Analytics Server component.

MitigationApply the relevant Oracle patch for CVE-2023-21952. If a patch is unavailable, restrict network access to the Analytics Server to trusted users only and implement additional authentication layers to mitigate the low-privilege exploitation vector.

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 Analytics Server version
    Check the installed version of Oracle Business Intelligence Enterprise Edition. This is typically found in the Oracle BI installation directory, often in a version file or through the Oracle BI Administration Tool. Common paths include: $ORACLE_HOME/bifoundation/server/config/ or check the bi_init.sh script for version information.
    Affected if The installed version is exactly 6.4.0.0.0
  2. Confirm Analytics Server HTTP endpoint is accessible
    Verify that the Analytics Server component is accessible over HTTP/HTTPS. This is typically accessed through the Oracle BI Presentation Server URL (often on ports 7001, 9500, or similar). Check if the /analytics/ or /saw.dll endpoint responds.
    Affected if The Analytics Server HTTP endpoint is reachable from the network and responds to requests
  3. Check for path traversal vulnerability indicators
    Inspect web server logs and test for path traversal patterns in Analytics Server requests. Look for abnormal access to files outside the expected web root directories, particularly through URL parameters that might contain ../ sequences.
    Affected if Unusual path traversal patterns appear in logs or unauthorized file access is detected

If the installed Oracle Business Intelligence Enterprise Edition version is exactly 6.4.0.0.0 and the Analytics Server is accessible via HTTP, the environment is affected by this information disclosure vulnerability.

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 the relevant Oracle patch for CVE-2023-21952. If a patch is unavailable, restrict network access to the Analytics Server to trusted users only and implement additional authentication layers to mitigate the low-privilege exploitation vector.

Fix this in Business Intelligence Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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