dbcve.org
Common Applications CalendarApplication · Oracle

CVE-2020-2820

HIGH · 8.2 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 12.2.8 or later.
See remediation →
89/100
Remediation priority · High
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: Notes). Supported versions that are affected are 12.1.1-12.1.3 and 12.2.3-12.2.8. 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.0 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/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

Unauthenticated HTTP vulnerability in the Notes component of Oracle Common Applications Calendar (E-Business Suite versions 12.1.1-12.1.3 and 12.2.3-12.2.8). Allows attackers network access to compromise the Calendar application, achieving high confidentiality impact and low integrity impact via unauthorized access to critical data and limited update/insert/delete operations. Requires human interaction, suggesting exploitation likely involves tricking a legitimate user (e.g., reflected XSS or similar).

MitigationApply Oracle's Security Patch for CVE-2020-2820 immediately upon availability. Until patched, restrict network access to the Calendar application via firewall/WAF rules and monitor for indicators of compromise.

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.8

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. Confirm Oracle E-Business Suite version
    Log into Oracle Application Manager (OAM) or query the FND_PRODUCT_GROUPS table: SELECT release_name FROM fnd_product_groups; Alternatively, check the iSetup or about Oracle E-Business Suite page.
    Affected if The reported version falls within 12.1.1-12.1.3 or 12.2.3-12.2.8.
  2. Verify Calendar module is deployed
    Check if the Oracle Common Applications Calendar (CAC) module is installed and enabled. Query ICX_POR_PRODUCTS or use Oracle Application Manager to list installed modules.
    Affected if The Calendar module is present and active in the E-Business Suite instance.
  3. Identify HTTP accessibility of Calendar Notes endpoint
    Determine if the Calendar application is exposed via HTTP/HTTPS. Review web server configuration (Oracle HTTP Server or Oracle WebLogic) for URL mappings to /oa_html/cac/ or similar Notes-related paths. Check for unauthenticated access to Calendar URLs.
    Affected if The Calendar Notes component is accessible over HTTP without authentication.
  4. Check network exposure of Calendar application
    Review firewall, load balancer, or WAF configurations to determine if the Calendar application URLs are exposed to untrusted networks (internet-facing or DMZ).
    Affected if The Calendar application is reachable from untrusted network segments.

If the E-Business Suite version is within 12.1.1-12.1.3 or 12.2.3-12.2.8 AND the Calendar/Notes component is deployed and accessible via HTTP from untrusted networks, the environment is likely affected.

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.8
Interim mitigation

Apply Oracle's Security Patch for CVE-2020-2820 immediately upon availability. Until patched, restrict network access to the Calendar application via firewall/WAF rules and monitor for indicators of compromise.

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-2020-2820 — 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-2020-2820 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