E Business IntelligenceApplication · Oracle

CVE-2020-2809

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 E-Business Intelligence product of Oracle E-Business Suite (component: DBI Setups). 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 E-Business Intelligence. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle E-Business Intelligence, 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 E-Business Intelligence accessible data as well as unauthorized update, insert or delete access to some of Oracle E-Business Intelligence 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 · moderate confidence

Vulnerability in Oracle E-Business Intelligence DBI Setups component allowing unauthenticated remote attackers via HTTP to access, modify, or delete data. Requires human interaction (UI:R) and results in high confidentiality impact with scope changes affecting additional products.

MitigationApply Oracle Critical Patch Update (CPU) containing the fix for CVE-2020-2809. Restrict network access to Oracle E-Business Suite interfaces and implement additional authentication layers where feasible while awaiting patch deployment.

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
E Business IntelligenceApplication
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 Intelligence version
    Query the Oracle database for the version using SQL: SELECT version FROM apps.fnd_product_groups WHERE product_group_name LIKE 'Inteligen%'; OR check the OBIEE/Oracle BI Administration tool for the installed version. Alternatively, query FND tables: SELECT release_name FROM fnd_release;
    Affected if The version falls within >= 12.1.1 and <= 12.1.3
  2. Verify DBI Setups component is configured
    Check if the DBI (Data Browser Intelligence) Setups module is enabled in Oracle E-Business Suite. Query: SELECT parameter_name, parameter_value FROM icx_parameters WHERE parameter_name LIKE '%DBI%'; or check the Oracle Applications Manager (OAM) console for DBI module status.
    Affected if DBI Setups component is enabled and accessible
  3. Confirm HTTP access to Oracle E-Business Suite
    Check if HTTP listeners are enabled for Oracle E-Business Suite. Review Oracle HTTP Server (OHS) configuration files (httpd.conf, Oracle E-Business Suite context file) for DBI-related servlet mappings. Test connectivity: curl -I http://<hostname>/OA_HTML/DBI/ or similar endpoints.
    Affected if HTTP access is enabled and the DBI Setups URL path is accessible without authentication
  4. Check for unauthenticated access controls
    Review Oracle E-Business Suite function security settings for DBI Setups. Query: SELECT function_name, access_mode FROM wf_resources WHERE function_name LIKE '%DBI%'; Review Oracle Application Framework (OAF) security configuration files.
    Affected if DBI Setups functions permit unauthenticated or guest user access

Your environment is affected if Oracle E-Business Intelligence version is between 12.1.1 and 12.1.3, the DBI Setups component is enabled, and HTTP access to the DBI Setups interface is available 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.1.3
Interim mitigation

Apply Oracle Critical Patch Update (CPU) containing the fix for CVE-2020-2809. Restrict network access to Oracle E-Business Suite interfaces and implement additional authentication layers where feasible while awaiting patch deployment.

Fix this in E Business Intelligence Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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