dbcve.org
MarketingApplication · Oracle

CVE-2020-2860

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

CVE-2020-2860 is an unauthenticated remote vulnerability in Oracle E-Business Suite's Marketing Administration component (versions 12.1.1-12.1.3). The flaw allows unauthenticated attackers with network access via HTTP to access critical data or gain full data access within Oracle Marketing, as well as unauthorized update/insert/delete operations on some data. Exploitation requires human interaction and while targeting Oracle Marketing, attacks may impact additional products due to scope change.

MitigationApply Oracle's security patches for this vulnerability when available. Until then, restrict network access to Oracle Marketing endpoints via firewall or WAF rules and monitor for suspicious HTTP activity.

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. Verify Oracle E-Business Suite is installed
    Check for the presence of Oracle E-Business Suite application directories (typically under $ORACLE_HOME) or check Oracle Fusion Middleware/Application Server configurations
    Affected if Oracle E-Business Suite is not present on the system, the vulnerability does not apply
  2. Confirm Oracle Marketing version
    Access Oracle E-Business Suite version information through the Oracle Applications Manager (OAM) interface, or query the database tables FND_PRODUCT_GROUPS and FND_APPLICATION using SQL: SELECT APPLICATION_ID, APPLICATION_NAME FROM FND_APPLICATION WHERE APPLICATION_NAME LIKE '%Marketing%';
    Affected if The installed Oracle Marketing version falls outside the 12.1.1-12.1.3 range (either lower than 12.1.1 or higher than 12.1.3), the system is not affected by this specific CVE version range
  3. Check if Marketing Administration component is enabled
    Verify the Marketing module is configured and accessible by checking the Oracle E-Business Suite profile option 'FND_ENABLE_MKT_ADMIN' or by attempting to access the Marketing Administration responsibility through the E-Business Suite login. Check if the ICX_SESSIONS profile allows external access.
    Affected if The Marketing Administration component is not enabled or the Marketing responsibility is not assigned to any user, exploitation is not possible
  4. Verify network exposure of Oracle Marketing endpoints
    Review firewall rules, load balancer configurations, or reverse proxy settings that expose Oracle E-Business Suite HTTP ports (typically 8000-8009 or configured ports) to untrusted networks. Check if the Marketing servlet endpoints (such as /OA_HTML/mktg*) are accessible from the internet.
    Affected if The Oracle Marketing HTTP endpoints are accessible from untrusted networks without proper authentication barriers, the system is vulnerable to unauthenticated remote exploitation
  5. Audit HTTP access logs for suspicious Marketing requests
    Examine Apache/Oracle HTTP Server access logs (typically in $ORACLE_HOME/Apache/Apache/logs or Oracle WebTier logs) for unusual GET/POST requests targeting Marketing Administration URLs, especially from external IP addresses, anomalous parameter patterns, or automated scanning behavior.
    Affected if Unusual or unauthorized HTTP requests targeting Marketing Administration endpoints are found in the logs, this may indicate active exploitation attempts

A system is affected if it runs Oracle E-Business Suite with Oracle Marketing module enabled at version 12.1.1 through 12.1.3 and has the Marketing Administration endpoints exposed to network access.

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 security patches for this vulnerability when available. Until then, restrict network access to Oracle Marketing endpoints via firewall or WAF rules and monitor for suspicious HTTP activity.

Fix this in Marketing Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA2.0 h
22.0 hours of engineering $3,800
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,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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