CVE-2020-14666
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 Email Center product of Oracle E-Business Suite (component: Message Display). Supported versions that are affected are 12.1.1-12.1.3 and 12.2.3-12.2.9. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Email Center. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Email Center, 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 Email Center accessible data as well as unauthorized update, insert or delete access to some of Oracle Email Center 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 · high confidenceUnauthenticated vulnerability in Oracle Email Center's Message Display component (versions 12.1.1-12.1.3 and 12.2.3-12.2.9) allows remote attackers via HTTP to access or modify data without credentials. The attack requires human interaction (UI:R) and exhibits scope change (S:C), meaning attacks against Email Center may impact additional Oracle E-Business Suite products. High confidentiality impact with partial integrity impact.
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.3>= 12.2.3, <= 12.2.9CVSS 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.
-
Confirm Oracle Email Center installationCheck for Oracle Email Center in the Oracle Applications Manager (OAM) or query the Oracle E-Business Suite registry. On the application server, look for the 'mail' product component in the APPS schema or check the Oracle E-Business Suite version information.Affected if Oracle Email Center is not installed or not in use, then the CVE does not apply.
-
Identify installed Oracle Email Center versionRun the command 'select release_name from apps.fnd_product_groups;' or access the Oracle E-Business Suite About page via the Oracle Applications Manager. Alternatively, check the Oracle Email Center specific version in the Oracle E-Business Suite version information.Affected if The installed version falls within 12.1.1 through 12.1.3, or 12.2.3 through 12.2.9, indicating the environment is within the affected version range.
-
Verify Message Display component accessibilityCheck if the Message Display functionality in Oracle Email Center is accessible. This component handles the display of email messages within the application. Confirm whether the '/OA_HTML/ibmcstarterapps/' or related Message Display endpoints are accessible via the web tier.Affected if The Message Display component is accessible without authentication, which is required for exploitation.
-
Confirm HTTP listener exposureDetermine if the Oracle E-Business Suite web interfaces (Oracle HTTP Server) are configured and accessible via HTTP. Check the Oracle HTTP Server (OHS) configuration files and verify listener status. The vulnerability is exploitable over HTTP.Affected if The Oracle E-Business Suite is exposed via HTTP (rather than HTTPS only), increasing the risk of exploitation.
A defender is affected if Oracle Email Center is installed and running a version within 12.1.1-12.1.3 or 12.2.3-12.2.9, with the Message Display component accessible over HTTP.
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 the Oracle Critical Patch Update addressing CVE-2020-14666, or upgrade to a supported version of Oracle Email Center beyond the affected version range.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14666 — 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-14666 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