CVE-2022-22390
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 · uneditedIBM Db2 for Linux, UNIX and Windows 9.7, 10.1, 10.5, 11.1, and 11.5 may be vulnerable to an information disclosure caused by improper privilege management when table function is used. IBM X-Force ID: 221973.
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 · moderate confidenceIBM Db2 versions 9.7, 10.1, 10.5, 11.1, and 11.5 contain an information disclosure vulnerability stemming from improper privilege management when table functions are used. An authenticated attacker with limited privileges could potentially access sensitive data through table function calls that should be restricted based on their authorization level.
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= 9.7= 10.1= 10.5= 11.1= 11.5CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Identify installed Db2 versionRun 'db2level' or 'db2pd -version' command to get the exact Db2 version and fix pack levelAffected if The version is 9.7, 10.1, 10.5, 11.1, or 11.5 (any fix pack)
-
List all table functions in the databaseQuery SYSCAT.TABLEFUNCTIONS view: SELECT TABSCHEMA, TABNAME FROM SYSCAT.TABLEFUNCTIONSAffected if Any table functions exist in the database
-
Check privileges granted on table functionsQuery SYSCAT.TABLEFUNCPRIVS view: SELECT GRANTEE, TABSCHEMA, TABNAME, AUTH from SYSCAT.TABLEFUNCPRIVSAffected if Users with limited or restricted authorization levels have privileges (SELECT, EXECUTE) on table functions that expose sensitive data
-
Identify users with limited privileges accessing table functionsCompare granted privileges against user roles: SELECT GRANTEE, AUTH, TABSCHEMA, TABNAME FROM SYSCAT.TABLEFUNCPRIVS WHERE GRANTEE in (SELECT GRantee FROM SYSCAT.DBAUTH WHERE DBADMAUTH='N' or SYSADMAUTH='N')Affected if Users who should have restricted access (non-DBA users) have been granted privileges on table functions containing sensitive information
Your environment is affected if you run any of the listed Db2 versions (9.7, 10.1, 10.5, 11.1, 11.5) AND you have users with limited privileges who have been granted access to table functions that should be restricted based on their authorization level.
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 IBM security patch for CVE-2022-22390 and audit table function privileges to ensure users only have access to functions commensurate with their role, following least privilege principles.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22390 — 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-22390 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