dbcve.org
GoldengateApplication · Oracle

CVE-2022-21551

MEDIUM · 6.8 CVSS v3.1 Published 2022-07-19
Fix available
A fix is available. Upgrade to 19.1.0.0.220719 / 21.7.0.0.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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 Oracle GoldenGate (component: Oracle GoldenGate). The supported version that is affected is 21c: prior to 21.7.0.0.0; 19c: prior to 19.1.0.0.220719. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle GoldenGate. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of Oracle GoldenGate. CVSS 3.1 Base Score 6.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/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

A detailed technical summary for this CVE is being prepared.

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:>= 19.1.0.0.0, < 19.1.0.0.220719>= 21.1.0, < 21.7.0.0.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
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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
Upgrade available Upgrade to 19.1.0.0.220719 / 21.7.0.0.0 or later
Fixed in 19.1.0.0.22071921.7.0.0.0
Vendor patch www.oracle.com →
Recommended fix High confidence

19c: upgrade to 19.1.0.0.220719 or later; 21c: upgrade to 21.7.0.0.0 or later

  1. 1. Identify current Oracle GoldenGate version by running 'VERSION' command in GGSCI or checking the installation directory
  2. 2. Download the patched version from Oracle Support: 21c users download 21.7.0.0.0 or later, 19c users download 19.1.0.0.220719 or later
  3. 3. Stop all Oracle GoldenGate processes: ./GGSCI then 'STOP EXTRACT *', 'STOP REPLICAT *', then 'STOP MANAGER'
  4. 4. Create a complete backup of the Oracle GoldenGate home directory including parameter files, checkpoint files, and trail files
  5. 5. Install the patched version using Oracle Universal Installer (OUI) or apply the patch following Oracle's documentation
  6. 6. Verify the installation was successful by checking the new version matches the patched release
  7. 7. Start Oracle GoldenGate processes: start MANAGER, then start all EXTRACT and REPLICAT groups
  8. 8. Monitor the processes to ensure normal operation and verify data integrity
Caveat Review Oracle GoldenGate upgrade documentation for any configuration changes required between major versions; test thoroughly in non-production environment before applying to production

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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