CVE-2021-35652
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 Essbase Administration Services product of Oracle Essbase (component: EAS Console). The supported versions that are affected are Prior to 11.1.2.4.046 and Prior to 21.3. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Essbase Administration Services. While the vulnerability is in Essbase Administration Services, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Essbase Administration 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 confidenceUnauthenticated remote code execution vulnerability in Oracle Essbase Administration Services (EAS Console) allows attackers with network HTTP access to completely compromise the affected system, achieving full confidentiality, integrity, and availability takeover.
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< 11.1.2.4.046>= 21.0, < 21.3CVSS 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.
-
Confirm Oracle EAS Console is installedIdentify if Oracle Essbase Administration Services (EAS Console) is present in the environment. Check for EAS Console processes or installed components related to Oracle Essbase.Affected if EAS Console is installed and running
-
Determine EAS Console versionLocate and retrieve the installed version of Oracle Essbase Administration Services. This is typically available through the EAS Console interface, Oracle inventory, or installation directories.Affected if Version is < 11.1.2.4.046 or >= 21.0 and < 21.3
-
Verify network accessibility of EAS ConsoleCheck if the EAS Console HTTP service is exposed to the network. Review firewall rules, network configurations, and listening ports to determine if the EAS Console is accessible over HTTP/HTTPS from untrusted networks.Affected if EAS Console HTTP service is accessible from untrusted network segments
The system is affected if Oracle Essbase Administration Services is running with a version less than 11.1.2.4.046, or version 21.0 through 21.2, and the EAS Console is network-accessible via HTTP.
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 · scoped11.1.2.4.04621.3
Apply Oracle patch for version 11.1.2.4.046 or 21.3 and later. Restrict network access to EAS Console to trusted sources only as an interim control.
11.1.2.4.046 (11.x line) or 21.3 (21.x line)
- Review the Oracle Critical Patch Update October 2021 advisory at https://www.oracle.com/security-alerts/cpuoct2021.html for CVE-2021-35652 details
- Identify the current version of Essbase Administration Services (EAS) in your environment
- For 11.x versions: Plan upgrade to version 11.1.2.4.046 or later
- For 21.x versions: Plan upgrade to version 21.3 or later
- Download the patched version from Oracle Technology Network or My Oracle Support
- Test the upgrade in a non-production environment before deploying to production
- Apply the upgrade during a scheduled maintenance window
- Verify the EAS Console is functional post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35652 — 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-35652 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