dbcve.org
Common Applications CalendarApplication · Oracle

CVE-2020-2823

HIGH · 8.2 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 12.1.3 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. 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

A vulnerability in the Oracle Common Applications Calendar Notes component (versions 12.1.1-12.1.3) allows unauthenticated attackers with network access via HTTP to read, modify, or delete data in the Notes application. The attack requires human interaction from a person other than the attacker, suggesting it may involve social engineering or indirect exploitation through legitimate user actions.

MitigationApply Oracle Critical Patch Update (CPU) for April 2020 or later, which includes the security fix for CVE-2020-2823 in the Oracle E-Business Suite. Verify Calendar/Notes functionality post-patch.

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

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 database or check the application server for Oracle E-Business Suite version using SQL: SELECT version FROM apps.fnd_product_groups; or check the APPL_TOP directory for version files.
    Affected if The installed version is not confirmed or is within the 12.1.1 to 12.1.3 range.
  2. Check Calendar module version
    Query the Oracle Applications tables: SELECT patch_level FROM fnd_product_installations WHERE product LIKE '%CALENDAR%'; or check the Oracle Diagnostics log for Calendar module patch level.
    Affected if The Calendar module version falls between 12.1.1 and 12.1.3 inclusive.
  3. Verify Notes component is enabled
    Check Oracle Applications Manager (OAM) or query fnd_application for application_id 801 (Notes), then verify it is not disabled in the Oracle EBS profile options: SELECT option_value FROM fnd_profile_options WHERE profile_option_name = 'CALENDAR_ENABLED';
    Affected if The Notes component (application ID 801) is enabled and accessible in the Oracle EBS environment.
  4. Confirm HTTP network accessibility
    Attempt to access the Calendar/Notes endpoint through the Oracle EBS HTTP server URL pattern: /OA_HTML/rdNotes.html or /OA_HTML/caldwnld.jsp. Check if these endpoints respond without authentication.
    Affected if The Notes application endpoints are reachable over HTTP/HTTPS without requiring authentication from the network.

The environment is affected if Oracle E-Business Suite with Calendar/Notes component version 12.1.1 through 12.1.3 is installed, the Notes module is enabled, and the HTTP interface is network-accessible, as the flaw requires unauthenticated HTTP access combined with human interaction to exploit.

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

Apply Oracle Critical Patch Update (CPU) for April 2020 or later, which includes the security fix for CVE-2020-2823 in the Oracle E-Business Suite. Verify Calendar/Notes functionality post-patch.

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-2823 — 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-2823 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