Common Applications CalendarApplication · Oracle

CVE-2021-2114

HIGH · 8.2 CVSS v3.1 Published 2021-01-20
Fix available
A fix is available. Upgrade to after 12.2.10 or later.
See remediation →
89/100
Remediation priority · High
High EPSS 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 Oracle Common Applications Calendar product of Oracle E-Business Suite (component: Applications Calendar). Supported versions that are affected are 12.1.1-12.1.3 and 12.2.3-12.2.10. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Common Applications Calendar. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Common Applications Calendar, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Common Applications Calendar accessible data as well as unauthorized update, insert or delete access to some of Oracle Common Applications Calendar accessible data. CVSS 3.1 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/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 unauthenticated HTTP vulnerability in Oracle E-Business Suite's Common Applications Calendar component affecting versions 12.1.1-12.1.3 and 12.2.3-12.2.10. The CVSS vector indicates network-exploitable with low complexity and required human interaction, likely pointing to an injection flaw (SQL or other) that allows unauthorized access to sensitive data and limited modify/delete operations.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for CVE-2021-2114 to the E-Business Suite Calendar module. If immediate patching is not feasible, restrict network access to the Calendar application through firewall or web application firewall rules.

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
Common Applications CalendarApplication
Affected:>= 12.1.1, <= 12.1.3>= 12.2.3, <= 12.2.10

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
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/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 E-Business Suite installation
    Query the Oracle Applications tables (e.g., FND_PRODUCT_GROUPS) or check Oracle Application Manager (OAM) to confirm E-Business Suite is installed and obtain the base version number.
    Affected if E-Business Suite is not installed or not at a version that includes the Calendar module.
  2. Locate the Common Applications Calendar module version
    Use Oracle Application Manager or query the Oracle patch history (e.g., AD_PATCH_DRIVERS or FND_APPL_TOPS) to identify the installed version of the Common Applications Calendar component.
    Affected if The Calendar module version cannot be determined or the module is not present.
  3. Compare Calendar version to affected ranges
    Compare the identified Calendar module version against the affected ranges: 12.1.1 to 12.1.3 OR 12.2.3 to 12.2.10.
    Affected if The installed version falls within either 12.1.1-12.1.3 or 12.2.3-12.2.10.
  4. Verify HTTP interface accessibility
    Attempt to access the Calendar servlet endpoint (typically /OA_HTML/cal/, /OA_HTML/ical/, or similar Calendar-related URLs) without authentication via HTTP/HTTPS from a network location.
    Affected if The Calendar HTTP endpoints are reachable without authentication.
  5. Confirm unauthenticated endpoint exposure
    Review the Oracle E-Business Suite congruent site configuration and web listener settings (check Oracle HTTP Server or Oracle WebLogic configuration files) to verify that Calendar-related servlets are mapped and accessible without requiring Oracle Applications session credentials.
    Affected if Calendar servlets are mapped in the web listener and accessible without Oracle Apps authentication.

A user is affected if Oracle E-Business Suite with the Common Applications Calendar module is installed with a version between 12.1.1-12.1.3 or 12.2.3-12.2.10 and the Calendar HTTP interface is network-accessible without authentication.

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
Upgrade available Upgrade to a release after 12.2.10
Interim mitigation

Apply the relevant Oracle Critical Patch Update (CPU) for CVE-2021-2114 to the E-Business Suite Calendar module. If immediate patching is not feasible, restrict network access to the Calendar application through firewall or web application firewall rules.

Fix this in Common Applications Calendar 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 the upgrade done

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-2114 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-2114 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