MarketingApplication · Oracle

CVE-2020-14875

CRITICAL · 9.1 CVSS v3.1 Published 2020-10-21

Fix available

A fix is available. Upgrade to after 12.2.10 or later.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

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 of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Marketing accessible data as well as unauthorized access to critical data or complete access to all Oracle Marketing accessible data. CVSS 3.1 Base Score 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).

Technical summary

dbcve analysis · high confidence

Unauthenticated HTTP vulnerability in Oracle E-Business Suite Marketing Administration component allows remote attackers to create, delete, or modify critical data as well as access all data within the Oracle Marketing module. The flaw is easily exploitable via network with no privileges or user interaction required.

MitigationApply Oracle Critical Patch Update (CPU) or specific security patch for CVE-2020-14875. If immediate patching is not possible, restrict network access to Oracle Marketing administration interfaces via firewall or web application firewall.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

MarketingApplication

Affected:>= 12.1.1, <= 12.1.3>= 12.2.3, <= 12.2.10

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify Oracle E-Business Suite version

Query the Oracle applications context file or run 'select release_name from apps.fnd_product_groups' to get the E-Business Suite release version

Affected if The installed version falls within 12.1.1 to 12.1.3 OR 12.2.3 to 12.2.10
Confirm Marketing module installation

Query the Oracle database: 'select application_short_name, product_version from fnd_product_installations where application_short_name in (''MKT'', ''AK'')' or check via Oracle Application Manager

Affected if The Marketing module (MKT) or Marketing extension (AK) is installed and active
Verify Marketing Administration component is accessible

Check if the /marketing/admin or /oa_servlets/oracle/apps/marketing/ administration endpoints are available via HTTP on the Oracle E-Business Suite web ports (typically 8000-8003)

Affected if The Marketing Administration HTTP interface responds without authentication or can be accessed without login credentials
Check network exposure of Oracle E-Business Suite web interfaces

Review firewall rules, load balancer configurations, or perform a port scan to determine if Oracle HTTP Server ports (default 8000, 443, 8001 for OAAM) are exposed to untrusted networks or the public internet

Affected if The Oracle E-Business Suite web ports are accessible from untrusted networks without proper network segmentation or WAF protection

A system is affected if it runs Oracle E-Business Suite version 12.1.1-12.1.3 or 12.2.3-12.2.10 with the Marketing module installed and its Administration interface is network-accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 12.2.10

Interim mitigation

Apply Oracle Critical Patch Update (CPU) or specific security patch for CVE-2020-14875. If immediate patching is not possible, restrict network access to Oracle Marketing administration interfaces via firewall or web application firewall.

Recommended fix High confidence

Oracle E-Business Suite 12.1.4+ (12.1.x line) or 12.2.11+ (12.2.x line)

Confirm the current Oracle E-Business Suite 12.1.x or 12.2.x version using the Oracle Applications Manager (OAM) or by querying the database: SELECT RELEASE_NAME FROM FND_PRODUCT_GROUPS;
For Oracle E-Business Suite 12.1.x: Upgrade to version 12.1.4 or later, which includes the fix for CVE-2020-14875
For Oracle E-Business Suite 12.2.x: Upgrade to version 12.2.11 or later, which includes the fix for CVE-2020-14875
Alternatively, apply the Oracle Critical Patch Update (CPU) for October 2020 or later that addresses this CVE
After upgrade or patching, validate the Marketing Administration module is functioning correctly
Verify the patch was applied successfully by checking the applied patches in ADOP (AutoPatch) or using the Oracle Enterprise Manager

Caveat Standard Oracle E-Business Suite upgrade considerations apply - test thoroughly in non-production first; regression testing of custom integrations with Marketing module is recommended

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Marketing Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing8.0 h
Review / QA3.0 h

23.0 hours of engineering $3,980

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,368.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-14875 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2020-14875?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 12.2.10 or later

Severity 9.1 Critical

Exploit likelihood EPSS, next 30 days 2.2%

Affects: Marketing

Remediation

A high-priority fix

Fix this in Marketing 23 hrs · Moderate

Typical engagement from $3,980

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2020-14875 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References