CVE-2022-22353
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 Big SQL on IBM Cloud Pak for Data 7.1.0, 7.1.1, 7.2.0, and 7.2.3 could allow an authenticated user with appropriate permissions to obtain sensitive information by bypassing data masking rules using a CREATE TABLE SELECT statement. IBM X-Force ID: 220480.
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 Big SQL on Cloud Pak for Data contains a vulnerability where authenticated users with appropriate permissions can bypass data masking rules by using a CREATE TABLE SELECT (CTAS) statement, allowing unauthorized access to sensitive information that should be masked.
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= 7.1.0= 7.1.1>= 7.2.0, <= 7.2.3= 7.2.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 the installed IBM Big SQL versionUse the Big SQL command line interface (bsql) or query the system catalog: SELECT * FROM SYSCAT.SOFTWAREVERSION or check the Cloud Pak for Data version via the cpd-cli tool: cpd-cli manage versionAffected if The installed version matches 7.1.0, 7.1.1, 7.2.0 through 7.2.3, or is exactly 7.2.3
-
Verify data masking rules are definedQuery the data masking metadata: SELECT * FROM SYSCAT.DATAMASKS or check the Cloud Pak for Data security policies for any defined masking rules on sensitive tablesAffected if Data masking rules exist and are defined for tables containing sensitive data
-
Check if CREATE TABLE SELECT (CTAS) is permitted for users with access to masked dataReview user permissions and roles in Big SQL: SELECT GRANTEE, TABNAME, PRIVILEGETYPE FROM SYSCAT.TABAUTH WHERE GRANTEE = '<user>' and examine if users with SELECT access can execute CTAS statementsAffected if Users with SELECT permission on masked tables can also execute CREATE TABLE AS SELECT statements
-
Test CTAS bypass of maskingAs an authenticated user with data access, run: CREATE TABLE new_table AS SELECT * FROM masked_table, then query the new table to see if unmasked data is accessibleAffected if The CTAS operation returns unmasked/sensitive data that should have been masked
You are affected if IBM Big SQL version 7.1.0, 7.1.1, 7.2.0-7.2.3 is running, data masking rules are defined, and authenticated users can execute CTAS statements that expose unmasked sensitive data.
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 · scopedUpgrade IBM Cloud Pak for Data to a patched version beyond 7.2.3. Review user permissions and data masking policies to ensure proper segregation of sensitive data.
Upgrade to Big SQL on Cloud Pak for Data 7.3.0 or later (or the latest available fix pack beyond 7.2.3)
- Contact IBM support or visit the official IBM support portal to obtain the fixed version for Big SQL on Cloud Pak for Data.
- Upgrade IBM Big SQL on Cloud Pak for Data to a version newer than 7.2.3 (e.g., 7.3.0 or later).
- After upgrading, verify that data masking rules are properly enforced by testing CREATE TABLE SELECT statements with masked columns.
- Review user permissions and ensure only authorized users have access to sensitive data.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22353 — 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-22353 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