dbcve.org
MarketingApplication · Oracle

CVE-2020-14817

HIGH · 8.2 CVSS v3.1 Published 2020-10-21
Fix available
A fix is available. Upgrade to after 12.2.10 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 and 12.2.3 - 12.2.10. 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.1 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/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

Unauthenticated HTTP vulnerability in Oracle Marketing Administration component of Oracle E-Business Suite allows remote attackers to gain unauthorized access to critical data and perform partial data modifications (insert/update/delete) on some accessible data. Exploitation requires human interaction (social engineering/luring victim to click malicious link).

MitigationApply Oracle Critical Patch Update (CPU) containing the fix for this vulnerability. Additionally, restrict network exposure of Oracle Marketing interfaces, implement WAF protection, 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>= 12.2.3, <= 12.2.10

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 Marketing module version
    Query the Oracle E-Business Suite version information. In the application tier, run: 'adident Header $OA_TOP/html/Marketing/<admin JSP file>' or check the patch level using 'opatch lsinventory' against the Marketing module patches.
    Affected if Version falls within 12.1.1 to 12.1.3 OR 12.2.3 to 12.2.10
  2. Verify HTTP access to Marketing Administration interface
    Check if the Oracle Marketing Administration web interface is exposed via HTTP/HTTPS. Inspect web server configuration (Oracle HTTP Server/OHS) for mounted paths related to '/marketing' or '/oa_servlets/icx' endpoints.
    Affected if The Marketing Administration component is network-accessible via HTTP without authentication barriers
  3. Confirm if CPU patch for CVE-2020-14817 is applied
    Run Oracle OPatch to check for the specific CPU patch: 'opatch lsinventory | grep -i <CVE-2020-14817-related-patch-id>' or review Oracle E-Business Suite patch history for the October 2020 CPU or subsequent updates.
    Affected if The October 2020 Critical Patch Update or later containing the fix has not been applied
  4. Review web access logs for suspicious unauthenticated requests
    Examine HTTP server access logs (typically in $ORACLE_HOME/Apache/logs) for unusual request patterns to Marketing servlet paths like '/oa_servlets/icx/marketing' or '/marketing/admin' from untrusted sources.
    Affected if Unauthenticated HTTP requests to Marketing Administration endpoints are logged from external IPs

A user is affected if Oracle Marketing module version is 12.1.1-12.1.3 or 12.2.3-12.2.10 AND the Marketing Administration component is exposed via HTTP AND the October 2020 CPU or later has not been 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.2.10
Interim mitigation

Apply Oracle Critical Patch Update (CPU) containing the fix for this vulnerability. Additionally, restrict network exposure of Oracle Marketing interfaces, implement WAF protection, and monitor for suspicious HTTP activity.

Fix this in Marketing Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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