dbcve.org
Essbase Analytic Provider ServicesApplication · Oracle

CVE-2021-2433

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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: Web Services). Supported versions that are affected are 11.1.2.4 and 21.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Essbase Analytic Provider Services. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Essbase Analytic Provider Services. CVSS 3.1 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

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

Unauthenticated remote attackers can send HTTP requests to Essbase Analytic Provider Services Web Services component to cause a denial of service, resulting in the service hanging or crashing repeatedly. The vulnerability affects versions 11.1.2.4 and 21.2, and requires only network access via HTTP with no authentication.

MitigationApply the relevant Oracle Critical Patch Update for CVE-2021-2433. Until patched, restrict network access to Essbase Analytic Provider Services or implement a WAF to filter malicious requests.

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= 21.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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
    Locate the Essbase installation directory or check Oracle inventory files for Essbase components. On Oracle systems, query the Oracle Inventory using 'opatch lsinventory' or check the Oracle Fusion Middleware inventory for Essbase entries.
    Affected if The product is not installed or the component is not present, then the system is not affected.
  2. Identify the installed Essbase version
    Check the version of the installed Essbase Analytic Provider Services. This can typically be found in the installation manifest, Oracle Inventory, or by querying the Essbase administration interface. Look for version strings matching 11.1.2.4 or 21.2.
    Affected if The installed version is 11.1.2.4 or 21.2, the system is potentially affected.
  3. Verify the Web Services component is enabled
    Check the Essbase Analytic Provider Services configuration to confirm the Web Services component is enabled. This is typically configured in the opmn.xml or similar Oracle Process Manager configuration file, or through the Essbase Administration Services console.
    Affected if The Web Services component is enabled and accessible, the vulnerability is exploitable.
  4. Check network exposure of the Web Services endpoint
    Identify the HTTP endpoint for Essbase Analytic Provider Services Web Services (typically accessible on port 9500-9506 or similar). Verify whether this endpoint is reachable from untrusted networks by reviewing firewall rules, load balancer configurations, or network ACLs.
    Affected if The Web Services HTTP endpoint is exposed to untrusted network paths without authentication, exploitation is possible.

The environment is affected if Oracle Essbase Analytic Provider Services versions 11.1.2.4 or 21.2 are installed with the Web Services component enabled and accessible over HTTP from untrusted networks.

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 Critical Patch Update for CVE-2021-2433. Until patched, restrict network access to Essbase Analytic Provider Services or implement a WAF to filter malicious requests.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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