MarketingApplication · Oracle

CVE-2020-2836

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 Marketing product of Oracle E-Business Suite (component: Marketing Administration). 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 Marketing. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Marketing, 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 Marketing accessible data as well as unauthorized update, insert or delete access to some of Oracle Marketing 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 Marketing Administration component of Oracle E-Business Suite 12.1.1-12.1.3 allows remote attackers to access or modify marketing data without credentials. Successful exploitation requires human interaction (social engineering), and while scoped to Oracle Marketing, the scope change indicates potential impact to additional products in the EBS environment. Provides high confidentiality impact (data access) and low integrity impact (data modification).

MitigationApply Oracle's Critical Patch Update (CPU) containing the fix for CVE-2020-2836. Until patches are applied, limit network exposure to the Oracle Marketing interface and implement user awareness training to mitigate the human interaction requirement for exploitation.

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
MarketingApplication
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
    Check for EBS installation by looking for Oracle application directories (typically $APPL_TOP) or query the database for AD_BUGS or FND_PRODUCT_INSTALLATIONS tables which contain version information.
    Affected if Oracle E-Business Suite is not found or this is a different Oracle product.
  2. Verify EBS version is within affected range
    Query the FND_PRODUCT_GROUPS table or use the Oracle AD Utilities (adident) to determine the exact EBS version. Also check FND_APPL_SHORT_NAMES for the MSC (Marketing) application.
    Affected if Version is 12.1.1, 12.1.2, or 12.1.3.
  3. Confirm Oracle Marketing module is enabled
    Query FND_APPLICATION and FND_RESPONSIBILITY tables to check if the MSC (Marketing) application and related responsibilities are enabled and assigned to users.
    Affected if MSC application is enabled and functional in the EBS environment.
  4. Check Marketing Administration HTTP access points
    Review Oracle E-Business Suite concurrent manager logs, Oracle HTTP Server (OHS) access logs, and Oracle WebLogic/OAF configurations for the /marketing/ or related servlets. Use Oracle EBS Access Tester or review mod_ossl configuration.
    Affected if Marketing Administration URLs are accessible via HTTP without authentication or through exposed EBS login pages.
  5. Inspect for applied patches addressing CVE-2020-2836
    Query the AD_BUGS table in the EBS database for patch identifiers related to this CVE (Oracle CPU patches for January 2020 or later). Also check opatch lsinventory on the application tier.
    Affected if No patches from Oracle CPU Jan 2020 or later addressing this CVE are applied.

A user is affected if Oracle E-Business Suite version 12.1.1-12.1.3 is running with the Marketing (MSC) module enabled and accessible via HTTP without the CPU Jan 2020 or later patches applied.

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's Critical Patch Update (CPU) containing the fix for CVE-2020-2836. Until patches are applied, limit network exposure to the Oracle Marketing interface and implement user awareness training to mitigate the human interaction requirement for exploitation.

Fix this in Marketing 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-2836 — 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-2836 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