CVE-2024-35160
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 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.
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 Watson Query and IBM Db2 Big SQL on Cloud Pak for Data suffer from insufficient session expiration, allowing authenticated users to obtain sensitive information through persisted sessions that do not timeout as intended.
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.3= 7.4= 7.5= 7.6= 1.8= 2.0= 2.1= 2.2CVSS 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 installed IBM Big SQL versionRun 'bigsql version' or check the Big SQL service pod/container version using 'oc get pods -n <namespace> -o jsonpath="{.items[*].spec.containers[*].image}"' and look for the Big SQL image tagAffected if The version listed is 7.3, 7.4, 7.5, or 7.6
-
Identify installed IBM Watson Query versionCheck the Watson Query service deployment using 'oc get deployment -n <namespace>' or query the Watson Query API endpoint '/api/version', or inspect the CP4D version via 'oc get CPDarchive -n <namespace>'Affected if The version listed is 1.8, 2.0, 2.1, or 2.2
-
Locate session timeout configurationSearch for session timeout settings in ConfigMaps or secret resources: 'oc get configmap -n <namespace> | grep -i session' and review application.properties or wasconfig.properties files in the Watson Query or Big SQL podsAffected if A session timeout value is configured but the 'invalidate-on-timeout' or equivalent session invalidation setting is missing or disabled
-
Verify session persistence behaviorLogin to Watson Query or Big SQL, note the session cookie or token, wait beyond the configured timeout period, then attempt to use the same session identifier to access protected resources without re-authenticationAffected if The session remains valid and authenticated after the configured inactivity timeout period has elapsed, indicating sessions are not being invalidated as intended
You are affected if you are running IBM Big SQL versions 7.3-7.6 or IBM Watson Query versions 1.8-2.2 on Cloud Pak for Data, and your sessions remain valid beyond the intended timeout period.
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 IBM-provided patches or configuration updates to implement proper session timeout policies, and ensure sessions are invalidated after the configured inactivity period.
- Consultation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35160 — 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-2024-35160 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