CVE-2020-2861
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 · uneditedVulnerability 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 confidenceCVE-2020-2861 is an unauthenticated vulnerability in Oracle E-Business Suite Marketing Administration component (versions 12.1.1-12.1.3) accessible via HTTP. The flaw allows remote attackers to gain unauthorized access to critical data and perform unauthorized updates, inserts, or deletes. Exploitation requires human interaction and while targeting Oracle Marketing, attacks may impact additional products due to scope change.
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>= 12.1.1, <= 12.1.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle E-Business Suite installationCheck for Oracle E-Business Suite by querying the database for the presence of APPS schema or checking for ORACLE_HOME directories containing ebus (for example, look in $ORACLE_HOME/ebus or check for FND_TOP environment variable)Affected if Oracle E-Business Suite is not installed - this CVE does not apply
-
Determine Oracle Marketing module versionQuery the Oracle database: SELECT version FROM applsys.aq$_monitor WHERE version LIKE '12.1%'; or check the Oracle Marketing patch level via OPatch: cd $ORACLE_HOME/../OA_MEDIA && opatch lsinventory | grep -i marketingAffected if The installed version falls within 12.1.1 through 12.1.3 inclusive - user is potentially affected
-
Verify Marketing Administration HTTP interface accessibilityCheck if the Marketing Administration console is accessible via HTTP/HTTPS. This is typically found at paths like /OA_HTML/rtl/xxl.jsp or /servlets/oracle.apps.xx. Inspect web server configuration files (like Oracle HTTP Server's httpd.conf or Oracle WebLogic's config.xml) for routes serving Marketing AdministrationAffected if The Marketing Administration interface is exposed via HTTP and accessible from network - exploitation is possible
-
Review access logs for Marketing Administration endpointsExamine web access logs (typically in $ORACLE_HOME/../oa_var/tech_st/local/log or Apache logs) for unusual or unauthorized POST/GET requests targeting Marketing-related servlets and JSPs (search for paths containing 'marketing', 'xxl', 'offering')Affected if Evidence of unauthorized access attempts or unexpected operations against Marketing Administration endpoints is found
A user is affected if Oracle E-Business Suite with Oracle Marketing module versions 12.1.1 through 12.1.3 is installed AND the Marketing Administration HTTP interface is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Update (CPU) for April 2020 or later. If immediate patching is not feasible, restrict network access to Oracle Marketing Administration interfaces via firewall or web application firewall until the patch can be applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2861 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-2861 in production — separate from our analysis above.
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.
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.
- 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