dbcve.org
Applications FrameworkApplication · Oracle

CVE-2020-2890

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 Applications Framework product of Oracle E-Business Suite (component: Diagnostics). Supported versions that are affected are 12.1.3 and 12.2.3-12.2.9. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Applications Framework. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Applications Framework, 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 Applications Framework accessible data as well as unauthorized update, insert or delete access to some of Oracle Applications Framework 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 Oracle E-Business Suite Applications Framework Diagnostics component (versions 12.1.3 and 12.2.3-12.2.9). Allows remote attackers with network access via HTTP to access critical sensitive data and perform unauthorized updates/inserts/deletes without credentials, but requires human interaction to trigger.

MitigationApply Oracle Critical Patch Update (CPU) January 2020 or later security patches addressing CVE-2020-2890 to the affected E-Business Suite instances.

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
Applications FrameworkApplication
Affected:>= 12.2.3, <= 12.2.9= 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. Check Oracle E-Business Suite version
    Log into Oracle E-Business Suite and navigate to Help > About Oracle Applications, or query the FND_PRODUCT_GROUPS or AWR version tables to confirm the exact release version.
    Affected if The installed version matches 12.1.3 or falls within 12.2.3 through 12.2.9 inclusive.
  2. Identify if Oracle Applications Framework Diagnostics component is enabled
    Check the Oracle E-Business Suite profile option 'FND: Diagnostics' (profile code FND_DIAGNOSTICS) - query SELECT PROFILE_OPTION_VALUE FROM FND_PROFILE_OPTION_VALUES WHERE PROFILE_OPTION_ID IN (SELECT PROFILE_OPTION_ID FROM FND_PROFILE_OPTIONS WHERE PROFILE_OPTION_NAME = 'FND_DIAGNOSTICS'); or check via Oracle System Administrator responsibility.
    Affected if The FND_DIAGNOSTICS profile is set to 'Enabled' or 'Yes' at any level.
  3. Verify HTTP accessibility of diagnostic endpoints
    Check if the Applications Framework diagnostic pages are accessible over HTTP by attempting to access the /OA_HTML/luDiagnose URL path or reviewing web server access logs for requests to diagnostic servlets.
    Affected if The diagnostic servlets respond to HTTP requests without requiring authentication.
  4. Check for recent unauthenticated HTTP access to diagnostic URLs
    Review web tier access logs (such as Oracle HTTP Server access logs or Apache access logs) for patterns like GET /OA_HTML/luDiagnose or similar diagnostic endpoint patterns without corresponding session authentication.
    Affected if Unauthenticated requests to diagnostic URLs appear in the access logs from network sources.

A user is affected if they run Oracle E-Business Suite versions 12.1.3 or 12.2.3-12.2.9 with the Applications Framework Diagnostics component enabled and network-accessible via HTTP without additional authentication controls.

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 (CPU) January 2020 or later security patches addressing CVE-2020-2890 to the affected E-Business Suite instances.

Fix this in Applications Framework Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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