dbcve.org
GoldengateApplication · Oracle

CVE-2018-2913

CRITICAL · 10.0 CVSS v3.0 Published 2018-10-17
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 GoldenGate component of Oracle GoldenGate (subcomponent: Monitoring Manager). Supported versions that are affected are 12.1.2.1.0, 12.2.0.2.0 and 12.3.0.1.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via TCP 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. Note: For Linux and Windows platforms, the CVSS score is 9.0 with Access Complexity as High. For all other platforms, the cvss score is 10.0. CVSS 3.0 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/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 confidence

Critical unauthenticated remote code execution vulnerability in Oracle GoldenGate's Monitoring Manager component allows a remote attacker with TCP network access to completely take over the GoldenGate instance. The CVSS 10.0 score indicates full compromise of confidentiality, integrity, and availability with no authentication or user interaction required.

MitigationApply Oracle Critical Patch Update (CPU) for CVE-2018-2913 to affected versions 12.1.2.1.0, 12.2.0.2.0, and 12.3.0.1.0. As an interim measure, restrict network access to Monitoring Manager ports and implement monitoring for suspicious 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
GoldengateApplication
Affected:= 12.1.2.1.0= 12.2.0.2.0= 12.3.0.1.0

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
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/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 checks

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

  1. Identify if Oracle GoldenGate is installed
    Search for GoldenGate installation directories or check for 'ggsci' command in PATH. Common locations include /opt/oracle/ogg, $ORACLE_HOME/ogg, or installation-specific directories.
    Affected if GoldenGate software is present on the system
  2. Determine installed GoldenGate version
    Run 'ggsci' command and look for version information in the output, or check for version files in the installation directory such as a version.txt or manifest file.
    Affected if Installed version matches 12.1.2.1.0, 12.2.0.2.0, or 12.3.0.1.0 exactly
  3. Verify Monitoring Manager component is configured
    Check for Monitoring Manager process (often named 'mgr' or 'Manager') running via 'ps aux | grep -i mgr' or 'ps aux | grep -i manager'. Also inspect GoldenGate parameter files for MANAGER configuration entries.
    Affected if Monitoring Manager process is running or configured in GoldenGate parameter files
  4. Confirm network exposure of Monitoring Manager
    Check GoldenGate configuration files (typically in the dirprm directory) for PORT parameter in MGR parameter files. Use 'netstat -anp' or 'ss -tlnp' to verify if the configured Management Manager port is listening on a network-accessible interface.
    Affected if Monitoring Manager port is listening on 0.0.0.0 or an external IP rather than localhost only, and is reachable from untrusted networks

If Oracle GoldenGate versions 12.1.2.1.0, 12.2.0.2.0, or 12.3.0.1.0 are installed with the Monitoring Manager component exposed to network access, the environment is vulnerable to unauthenticated remote code execution.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Interim mitigation

Apply Oracle Critical Patch Update (CPU) for CVE-2018-2913 to affected versions 12.1.2.1.0, 12.2.0.2.0, and 12.3.0.1.0. As an interim measure, restrict network access to Monitoring Manager ports and implement monitoring for suspicious activity.

Recommended fix Moderate confidence

Oracle GoldenGate 12.3.0.2.x or later (or 18c/19c/21c/23c series)

  1. Review the October 2018 Critical Patch Update (CPU) at http://www.oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html for Oracle GoldenGate patches
  2. Identify the appropriate patch for your specific GoldenGate version (12.1.2.1.0, 12.2.0.2.0, or 12.3.0.1.0) from the advisory
  3. Download and apply the corresponding security patch from Oracle Support
  4. Alternatively, upgrade to a newer Oracle GoldenGate version (12.3.0.2.x or later, or the 18c/19c/21c/23c series) which includes the fix
  5. After patching or upgrading, verify the Monitoring Manager component is properly functioning
  6. Restart GoldenGate processes as required by the patch installation
Caveat When upgrading major versions (e.g., from 12.x to 18c+), review compatibility matrix and may require reconfiguration of processes

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

Fix this in Goldengate Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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