CVE-2020-14705
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 GoldenGate product of Oracle GoldenGate (component: Process Management). The supported version that is affected is Prior to 19.1.0.0.0. Easily exploitable vulnerability allows unauthenticated attacker with access to the physical communication segment attached to the hardware where the Oracle GoldenGate executes to compromise Oracle GoldenGate. While the vulnerability is in Oracle GoldenGate, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Oracle GoldenGate. CVSS 3.1 Base Score 9.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).
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-14705 is a critical vulnerability in Oracle GoldenGate's Process Management component affecting versions prior to 19.1.0.0.0. An unauthenticated attacker with adjacent network access to the physical communication segment can exploit this low-complexity flaw to achieve full takeover of Oracle GoldenGate, with potential impact to 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< 19.1.0.0.0CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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 GoldenGate installationLocate Oracle GoldenGate installation directories. Common paths include $ORACLE_HOME/goldengate, /u01/app/oracle/product/, or check for ggsci executable using 'which ggsci' or 'find / -name ggsci 2>/dev/null'Affected if Oracle GoldenGate is not found on the system - you are not affected by this specific CVE
-
Identify installed GoldenGate versionRun the GoldenGate Software Command Interface (ggsci) with the 'VERSION' command, or check for a version file in the installation directory such as 'VERSION' or 'README.txt'Affected if The version displayed is less than 19.1.0.0.0 - you are running a vulnerable version
-
Compare version against affected rangeIf using ggsci, execute it and run 'VERSION' to see full version details. Compare the version string against 19.1.0.0.0 using semantic version comparison (any version prior to 19.1.0.0.0 is affected)Affected if Version string begins with anything less than 19.1 (such as 12.x, 18.x, or 19.0.x) - the vulnerability is present
-
Assess network exposure to communication segmentDetermine if the GoldenGate communication segment (used for Extract and Replicat processes) is accessible from adjacent networks. Check network configuration, firewall rules, and listening ports (commonly 7809-7812 for Manager, additional ports for Extract/Replicat)Affected if The physical communication segment is reachable from untrusted adjacent networks without proper network segmentation - exploitation is possible
You are affected if Oracle GoldenGate is installed with a version prior to 19.1.0.0.0 and the communication segment has adjacent network exposure.
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.
dbcve · scoped19.1.0.0.0
Upgrade Oracle GoldenGate to version 19.1.0.0.0 or later to remediate this vulnerability. Until patched, restrict physical/network access to the communication segment and segment Oracle GoldenGate infrastructure.
Oracle GoldenGate 19.1.0.0.0 or later
- 1. Review Oracle GoldenGate 19.1.0.0.0 release notes and upgrade documentation for compatibility requirements
- 2. Perform a full backup of all GoldenGate configurations, parameter files, and trail files
- 3. Stop all GoldenGate processes (extracts and replicats) cleanly before upgrading
- 4. Upgrade Oracle GoldenGate to version 19.1.0.0.0 or later
- 5. Verify the upgrade was successful by checking the GoldenGate version
- 6. Restart GoldenGate processes and verify normal operation
- 7. Monitor for any anomalies and review audit logs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14705 — 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-14705 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