CVE-2024-35160: IBM Watson Query on Cloud Pak for Data 1.8, 2.0, 2.1, 2.2 and IBM Db2 Big SQL on Cloud Pak for Data 7.3, 7.4,

Routine

MEDIUM 4.3DOWNGRADEDOWNGRADE

CVE-2024-35160 is a medium-severity flaw (CVSS 4.3) affecting big sql, watson query with cloud pak for data. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

IBM Watson Query on Cloud Pak for Data 1.8, 2.0, 2.1, 2.2 and IBM Db2 Big SQL on Cloud Pak for Data 7.3, 7.4, 7.5, and 7.6 could allow an authenticated user to obtain sensitive information due to insufficient session expiration.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.4% (top 71%)
CISA exploited list	No
Weakness	CWE-613
Published	2024-11-23
Last modified	2026-06-17

Publisher (CNA): IBM Corporation · Vendor: ibm

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-11-23 14:15 UTCPublished CVE record published
2026-06-17 07:34 UTCUpdated Record last modified

ibm big sql DOWNGRADE

Affected: 7.3 · 7.4 · 7.5 · 7.6

Fixed in: no fixed release known

Safe to downgrade to: a release before 7.3

1. Check installed version

apt-cache policy big-sql || rpm -q big-sql || big-sql --version

2. No fixed release: DOWNGRADE to a release before 7.3 (Debian / Ubuntu)

apt-cache madison big-sql sudo apt install big-sql=<VERSION_BEFORE_7.3> sudo apt-mark hold big-sql

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list big-sql sudo dnf downgrade big-sql-<VERSION_BEFORE_7.3> sudo dnf versionlock add big-sql

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

ibm watson query with cloud pak for data DOWNGRADE

Affected: 1.8 · 2.0 · 2.1 · 2.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.8

1. Check installed version

apt-cache policy watson-query-with-cloud-pak-for-data || rpm -q watson-query-with-cloud-pak-for-data || watson-query-with-cloud-pak-for-data --version

2. No fixed release: DOWNGRADE to a release before 1.8 (Debian / Ubuntu)

apt-cache madison watson-query-with-cloud-pak-for-data sudo apt install watson-query-with-cloud-pak-for-data=<VERSION_BEFORE_1.8> sudo apt-mark hold watson-query-with-cloud-pak-for-data

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list watson-query-with-cloud-pak-for-data sudo dnf downgrade watson-query-with-cloud-pak-for-data-<VERSION_BEFORE_1.8> sudo dnf versionlock add watson-query-with-cloud-pak-for-data

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-35160?

big sql: downgrade or apply the listed mitigation; watson query with cloud pak for data: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-35160 being exploited?

CVE-2024-35160 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-35160 affect?

CVE-2024-35160 affects big sql, watson query with cloud pak for data. Severity is medium (CVSS 4.3). IBM Watson Query on Cloud Pak for Data 1.8, 2.0, 2.1, 2.2 and IBM Db2 Big SQL on Cloud Pak for Data 7.3, 7.4, 7.5, and 7.6 could allow an authenticated user to obtain sensitive information due to insufficient session expiration.

How urgent is CVE-2024-35160?

Priority 22/100. No elevated risk signals yet.

References

← Back to latest CVEs