dbcve.org
Essbase Analytic Provider ServicesApplication · Oracle

CVE-2021-2435

HIGH · 8.1 CVSS v3.1 Published 2021-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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 Essbase Analytic Provider Services product of Oracle Essbase (component: JAPI). The supported version that is affected is 11.1.2.4. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Essbase Analytic Provider Services. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Essbase Analytic Provider Services accessible data as well as unauthorized access to critical data or complete access to all Essbase Analytic Provider Services accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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

Vulnerability in Oracle Essbase Analytic Provider Services JAPI component allowing unauthenticated network attackers via HTTP to create, delete, or modify critical data, plus access all accessible data. The requirement for human interaction (UI:R) suggests the attack may involve tricking a legitimate user into triggering the malicious request.

MitigationApply Oracle's relevant security patch when available. Until then, restrict network access to Essbase Analytic Provider Services to trusted users only, as the vulnerability is exploitable over HTTP without authentication.

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
Essbase Analytic Provider ServicesApplication
Affected:= 11.1.2.4

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Confirm Oracle Essbase Analytic Provider Services is installed
    Check your system for the presence of Oracle Essbase software. Look for the product directory in the Oracle middleware home, typically under the Essbase folder. You can also query the Oracle inventory if available.
    Affected if The product is not installed on the system.
  2. Determine the installed version of Essbase Analytic Provider Services
    Run the appropriate version query command for your Oracle installation. This may be found in the Oracle Enterprise Manager, or by checking the product-specific version file in the installation directory. Compare your installed version against 11.1.2.4.
    Affected if The installed version is exactly 11.1.2.4.
  3. Verify if the JAPI component is enabled and running
    Check the Analytic Provider Services configuration. JAPI is the Java API component. Verify whether the JAPI service is configured and active in your Essbase environment.
    Affected if The JAPI component is enabled and running.
  4. Check if HTTP listener for Analytic Provider Services is exposed
    Inspect the network configuration for the Analytic Provider Services HTTP endpoint. Verify whether the HTTP port used by Essbase Analytic Provider Services is accessible over the network.
    Affected if The HTTP endpoint is exposed and accessible over the network.
  5. Assess network access to the vulnerable service
    Review your firewall rules and network access controls. Determine if the Analytic Provider Services HTTP port can be reached by untrusted or anonymous network attackers.
    Affected if The service is accessible from untrusted network segments without authentication.

You are affected if Oracle Essbase Analytic Provider Services version 11.1.2.4 is installed with the JAPI component enabled and its HTTP interface is exposed to untrusted network access.

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 relevant security patch when available. Until then, restrict network access to Essbase Analytic Provider Services to trusted users only, as the vulnerability is exploitable over HTTP without authentication.

Fix this in Essbase Analytic Provider Services Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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