IBM Support

Security Bulletin: IBM Watson Query on IBM Cloud does not govern all of the columns of a published object

Security Bulletin


Summary

IBM Watson Query on IBM Cloud integrates with IBM Knowledge Catalog (IKC) - formerly Watson Knowledge Catalog (WKC) - to enforce data protection rules on governed objects. When you publish objects from Watson Query to catalogs or projects, only the first 100 columns are registered in the catalog metadata and profiled. As a result, IBM Knowledge Catalog data protection rules are not enforced on columns 101 and above, and only the first 100 columns will be made subject to governance. The object must be published from Watson Query to be impacted. Objects added as connected assets or discovered via Metadata Import are not impacted.

Vulnerability Details

CVEID:   CVE-2024-37526
DESCRIPTION:   IBM Watson Query on Cloud Pak for Data could allow an authenticated user to obtain sensitive information from objects published using Watson Query due to an improper data protection mechanism.
CVSS Base score: 6.5
CVSS Temporal Score: See: https://exchange.xforce.ibmcloud.com/vulnerabilities/294285 for the current score.
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N)

Affected Products and Versions

Affected Product(s)Version(s)
IBM Watson Query on IBM Cloud

2.0.0 - 2.1.3

Remediation/Fixes

IBM strongly recommends performing the remediation steps now. Objects created and published to a governed catalog from Watson Query prior to June 25, 2024 need to be remediated.

To identify the version of your Watson Query instance, you can perform the following query: SELECT VALUE FROM DVSYS.INSTANCE_INFO WHERE KEY='DV_VERSION'; Note that regardless of your current version, any objects with more than 100 columns that were published to a catalog on or before June 25, 2024 are considered affected.

Affected Product(s)

Version(s)

Remediation/Fix/Instructions

IBM Watson Query on IBM Cloud

2.0.0 - 2.1.3

Identify all Watson Query objects with more than 100 columns created before June 25, 2024 by executing the following query:

SELECT sc.TABSCHEMA, sc.TABNAME, st.CREATE_TIME, COUNT(*) AS TOTAL_COLS FROM SYSCAT.COLUMNS as sc LEFT JOIN SYSCAT.TABLES as st ON sc.TABSCHEMA=st.TABSCHEMA AND sc.TABNAME=st.TABNAME WHERE sc.TABSCHEMA NOT LIKE 'IBM%' AND sc.TABSCHEMA NOT LIKE 'SYS%' AND st.CREATE_TIME < '2024-06-26' GROUP BY sc.TABSCHEMA, sc.TABNAME, st.CREATE_TIME HAVING COUNT(*) > 100;

 

For each returned object:

  1. Identify the ones that have been published to governed catalogs.
  2. Re-publish them and delete the original catalog asset depending on your configured catalog de-duplication logic.
  3. To confirm the correct number of columns is subject to governance, open the “Profile” tab of the catalog asset and confirm the correct number of columns is displayed at the top.

Workarounds and Mitigations

None

Get Notified about Future Security Bulletins

Subscribe to My Notifications to be notified of important product support alerts like this.

References

Complete CVSS v3 Guide
On-line Calculator v3

Off

Related Information

IBM Secure Engineering Web Portal
IBM Product Security Incident Response Blog

Acknowledgement

Change History

04 Oct 2024: Initial Publication

*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.

Disclaimer

According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES ""AS IS"" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. In addition to other efforts to address potential vulnerabilities, IBM periodically updates the record of components contained in our product offerings. As part of that effort, if IBM identifies previously unidentified packages in a product/service inventory, we address relevant vulnerabilities regardless of CVE date. Inclusion of an older CVEID does not demonstrate that the referenced product has been used by IBM since that date, nor that IBM was aware of a vulnerability as of that date. We are making clients aware of relevant vulnerabilities as we become aware of them. "Affected Products and Versions" referenced in IBM Security Bulletins are intended to be only products and versions that are supported by IBM and have not passed their end-of-support or warranty date. Thus, failure to reference unsupported or extended-support products and versions in this Security Bulletin does not constitute a determination by IBM that they are unaffected by the vulnerability. Reference to one or more unsupported versions in this Security Bulletin shall not create an obligation for IBM to provide fixes for any unsupported or extended-support products or versions.

Document Location

Worldwide

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSK1AQ","label":"IBM Data Virtualization"},"Component":"","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF043","label":"Red Hat"},{"code":"PF040","label":"RedHat OpenShift"}],"Version":"2.0.0-2.1.3","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 October 2024

Initial Publish date:
04 October 2024

UID

ibm17172306

Page Feedback