CVE-2022-21442
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 Oracle GoldenGate (component: OGG Core Library). The supported version that is affected is Prior to 23.1. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle GoldenGate executes to compromise Oracle GoldenGate. While the vulnerability is in Oracle GoldenGate, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle GoldenGate. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/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 confidenceLocal privilege escalation vulnerability in Oracle GoldenGate's OGG Core Library affecting versions prior to 23.1. A low-privileged attacker with local access to the infrastructure can exploit this to achieve complete takeover of Oracle GoldenGate, with potential scope expansion to impact additional products.
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< 23.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Locate Oracle GoldenGate installationSearch for Oracle GoldenGate directories or executables on the system (common locations include /opt/oracle, $ORACLE_HOME, or C:\Oracle\Middleware)Affected if Oracle GoldenGate installation directories or binaries are found on the system
-
Determine installed GoldenGate versionRun the GoldenGate version command (such as 'ggsci -v' or 'ggversion') from the installation directory, or inspect version files within the softwareAffected if The installed version number is below 23.1
-
Verify OGG Core Library presenceCheck for the presence of OGG Core Library files within the GoldenGate installation structureAffected if The OGG Core Library component is present in the installation
-
Identify running GoldenGate processesList running processes related to GoldenGate (such as extract, replicat, or manager processes) using system tools like ps or tasklistAffected if GoldenGate processes are running on the system
The environment is affected if Oracle GoldenGate is installed with a version prior to 23.1 and the OGG Core Library component is present.
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 · scoped23.1
Upgrade Oracle GoldenGate to version 23.1 or later. As this is a critical data replication infrastructure component, thorough testing in a non-production environment is essential before deployment.
23.1
- Verify current Oracle GoldenGate version using 'ggsci' command and 'VERSION' or 'INFO ALL'
- Review Oracle GoldenGate 23.1 installation documentation for prerequisites
- Ensure backup of GoldenGate configuration, checkpoint files, and trail files
- Stop all GoldenGate processes using 'STOP ER *' command
- Install Oracle GoldenGate 23.1 (or latest 23.x release) following Oracle's upgrade documentation
- Verify integrity of configuration files after upgrade
- Start GoldenGate processes using 'START ER *' command
- Verify replication is functioning correctly with 'INFO ALL' and 'LAG' commands
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21442 — 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-2022-21442 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