CVE-2021-2115
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 Oracle Common Applications Calendar product of Oracle E-Business Suite (component: Tasks). Supported versions that are affected are 12.1.1-12.1.3 and 12.2.3-12.2.10. Easily exploitable vulnerability allows low privileged 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 7.6 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 · moderate confidenceVulnerability in Oracle E-Business Suite Common Applications Calendar (Tasks component) allows low-privileged attackers with network access via HTTP to access, modify, or delete calendar data. The attack requires human interaction (social engineering/phishing) and can result in unauthorized access to sensitive calendar information and data manipulation.
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>= 12.1.1, <= 12.1.3>= 12.2.3, <= 12.2.10CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle E-Business Suite installationRun the command: sqlplus APPS/<password>@<SID> select release_name from apps.fnd_product_groups; or check for Oracle E-Business Suite binaries in $APPL_TOP directoryAffected if Oracle E-Business Suite is not installed - not affected. If installed, continue to next check.
-
Determine Oracle Common Applications Calendar versionQuery: SELECT patch_level FROM applsys.fnd_patch_run_levels WHERE patch_level LIKE '%CALENDAR%'; or check the Oracle Applications Manager (OAM) interface for component versionsAffected if Version falls within 12.1.1 to 12.1.3 OR 12.2.3 to 12.2.10 - potentially affected. Continue to next check.
-
Verify Calendar Tasks module is enabledLog into Oracle E-Business Suite as System Administrator, navigate to Application > Register, confirm module 'CAL' or 'Calendar Tasks' status is 'Enabled'. Alternatively query: SELECT application_id, application_name, status FROM fnd_application WHERE application_name LIKE '%Calendar%';Affected if Calendar Tasks module is disabled - not affected. If enabled and version is in affected range, proceed to next check.
-
Check network accessibility of Calendar HTTP endpointsReview web server configuration (Oracle HTTP Server or Oracle WebLogic) for exposed URLs containing '/OA_HTML/cal/', '/CAL/', or '/oracle/apps/cal/'. Check firewall rules for inbound access to ports 8000-8009 or 443/80 on E-Business Suite hosts.Affected if Calendar HTTP endpoints are publicly accessible from untrusted networks - at higher risk. If only accessible from trusted internal networks, lower risk but still potentially affected if version is vulnerable.
User is affected if Oracle E-Business Suite with Oracle Common Applications Calendar is installed, version is 12.1.1-12.1.3 or 12.2.3-12.2.10, the Calendar Tasks module is enabled, and network access to Calendar HTTP interfaces is possible for low-privileged attackers.
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.
From vendor dataApply Oracle Critical Patch Update (CPU) patches for CVE-2021-2115 when released. In the interim, restrict network access to Oracle E-Business Suite Calendar interfaces and implement additional authentication controls for the Tasks module.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2021-2115 — 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-2115 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