CVE-2021-2244
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 Hyperion Analytic Provider Services product of Oracle Hyperion (component: JAPI) and Essbase Analytic Provider Services product of Oracle Essbase (component: JAPI). Supported versions that are affected are Hyperion Analytic Provider Services 11.1.2.4 and 12.2.1.4, and Essbase Analytic Provider Services 21.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Hyperion Analytic Provider Services. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Hyperion Analytic Provider Services, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Hyperion Analytic Provider Services. CVSS 3.1 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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 · high confidenceCritical unauthenticated remote code execution vulnerability in the JAPI component of Oracle Hyperion Analytic Provider Services and Essbase Analytic Provider Services. An attacker with network access via HTTP can achieve complete system compromise (full confidentiality, integrity, and availability impact), though the attack requires human interaction.
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= 21.2= 11.1.2.4= 12.2.1.4CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Oracle Analytic Provider Services productCheck for presence of either Oracle Essbase Analytic Provider Services or Oracle Hyperion Analytic Provider Services in the installed software inventory. Look in Oracle Fusion Middleware inventory directories or Windows installed programs list.Affected if Either Essbase Analytic Provider Services or Hyperion Analytic Provider Services is installed
-
Determine installed version of the productLocate the version information in the product's installation directory, Oracle inventory, or by querying the component directly. For Essbase APS check the opmn.xml or configuration files. For Hyperion APS check the deployment descriptors or registry entries.Affected if Version matches 21.2 for Essbase, or 11.1.2.4 or 12.2.1.4 for Hyperion Analytic Provider Services
-
Verify JAPI component is running and exposed via HTTPCheck if the Analytic Provider Services are running and listening on expected HTTP ports (typically 9080, 9443, or custom configured ports). Query the process list and netstat to identify listening HTTP services.Affected if JAPI component is running and bound to an HTTP listener accessible over the network
-
Confirm network accessibility of JAPI endpointTest HTTP access to the JAPI endpoint by attempting a connection to the service URL (typically /aps/JAPI or similar路径 under the Analytic Provider Services context). Verify if the port is exposed to untrusted networks.Affected if JAPI HTTP endpoint is reachable from untrusted network segments without authentication
Environment is affected if Oracle Essbase Analytic Provider Services version 21.2 OR Hyperion Analytic Provider Services versions 11.1.2.4 or 12.2.1.4 is installed AND the JAPI component is accessible via HTTP to untrusted users.
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) immediately. If patching is not immediately feasible, restrict network access to Hyperion/Essbase Analytic Provider Services to trusted users only.
Apply Oracle April 2021 CPU (CPUAPR2021) - Oracle patches are version-specific and delivered via patch numbers rather than new product versions
- 1. Navigate to Oracle Support and download the April 2021 Critical Patch Update (CPU) from https://www.oracle.com/security-alerts/cpuapr2021.html
- 2. Identify the specific patch(es) for Hyperion Analytic Provider Services and Essbase Analytic Provider Services from the CPU advisory
- 3. Review the patch prerequisites and installation instructions in the Oracle Critical Patch Update advisory
- 4. Back up the existing Oracle Hyperion/Essbase installation and database before applying any patches
- 5. Apply the relevant patch(es) to each affected system following Oracle's standard patching procedures
- 6. After patching, restart the affected services as instructed in the patch documentation
- 7. Verify the patch was applied successfully by checking the Oracle Opatch utility output
- 8. Test that Hyperion Analytic Provider Services and Essbase Analytic Provider Services are functioning normally post-patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-2244 — 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-2021-2244 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