Email CenterApplication · Oracle

CVE-2020-2813

HIGH · 8.2 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 12.2.9 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 Email Center product of Oracle E-Business Suite (component: KB Search). Supported versions that are affected are 12.1.1-12.1.3 and 12.2.3-12.2.9. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Email Center. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Email Center, 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 Email Center accessible data as well as unauthorized update, insert or delete access to some of Oracle Email Center 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 remote vulnerability in the KB Search component of Oracle Email Center (E-Business Suite versions 12.1.1-12.1.3 and 12.2.3-12.2.9) allows unauthenticated attackers via HTTP to access or modify data. The vulnerability requires human interaction and can impact additional products beyond Email Center due to scope change.

MitigationApply Oracle Critical Patch Update (April 2020) addressing CVE-2020-2813. If patching is delayed, restrict network access to Oracle Email Center and monitor for anomalous KB Search queries.

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
Email CenterApplication
Affected:>= 12.1.1, <= 12.1.3>= 12.2.3, <= 12.2.9

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 version
    Run the command 'select release_name from apps.fnd_product_groups;' or check the Oracle Applications Manager console for the version. Alternatively, check the $APPL_TOP/../oracle/apps/ia/html/RELEASE.txt file.
    Affected if Version falls within 12.1.1 to 12.1.3, or 12.2.3 to 12.2.9
  2. Confirm KB Search component is enabled
    Access Oracle Email Center through the applications menu (responsibility: Oracle Email Center > Setup > KB Search) or query the database: SELECT * FROM icx_parameters WHERE enabled_flag = 'Y';
    Affected if KB Search functionality is present and enabled in the Oracle Email Center responsibility
  3. Verify HTTP access to KB Search
    Attempt to access the KB Search endpoint via HTTP (typically /OA_HTML/ibix/.../search or /OA_HTML/center/kbsearch) without authentication, or check application layer configuration for exposed KB Search URLs.
    Affected if KB Search component is accessible over HTTP without authentication requirements
  4. Check network exposure
    Review load balancer, web tier, or firewall configurations to determine if Oracle Email Center KB Search URLs are reachable from untrusted networks. Use tools like netstat or review reverse proxy rules.
    Affected if The KB Search endpoint is exposed to the internet or untrusted internal networks without authentication barriers

If running an affected Oracle E-Business Suite version (12.1.1-12.1.3 or 12.2.3-12.2.9) with KB Search enabled and accessible via HTTP to untrusted users, the environment is vulnerable to CVE-2020-2813.

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

Apply Oracle Critical Patch Update (April 2020) addressing CVE-2020-2813. If patching is delayed, restrict network access to Oracle Email Center and monitor for anomalous KB Search queries.

Fix this in Email Center Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-2813 — 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-2020-2813 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