Skip to main content
VulnerabilityPublished

CVE-2024-39724: IBM Db2 Big SQL on Cloud Pak for Data · Unthrottled Resource Allocation

Affects IBM Db2 Big SQL on Cloud Pak for DataSource CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IBMDb2 Big SQL on Cloud Pak for DataAffected
  • ≥ IBM Db2 Big SQL 7.6 on Cloud Pak for Data 4.8, ≤ 2.1.0
  • =IBM Db2 Big SQL 7.7 on Cloud Pak for Data 5.0
  • =IBM Db2 Big SQL 7.8 on Cloud Pak for Data 5.1
Fixed in–

CPE configurations (3)

  • cpe:2.3:a:ibm:big_sql:7.6:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:big_sql:7.7:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:big_sql:7.8:*:*:*:*:*:*:*

AI-suggested

  1. Implement strict access controls and monitoring to limit authenticated user privileges, especially for users with internal system knowledge.
  2. Monitor resource usage patterns closely to detect abnormal spikes that could indicate exploitation attempts.
  3. Use rate limiting or resource quotas if supported by the platform to prevent any single user or process from consuming excessive resources.
  4. Segregate duties and enforce least privilege principles to reduce the number of users who can trigger resource-intensive operations.
  5. Regularly review and audit user activities and system logs for signs of misuse or attempts to exploit resource allocation.
  6. Engage with IBM support and subscribe to security advisories to obtain patches or workarounds as soon as they become available.
  7. Consider deploying additional infrastructure redundancy or failover mechanisms to maintain service availability during potential DoS events.
  8. Educate internal users about the risks of resource misuse and enforce policies to prevent accidental or malicious resource exhaustion.

Description

IBM Db2 Big SQL on Cloud Pak for Data versions 7.6 (on CP4D 4.8), 7.7 (on CP4D 5.0), and 7.8 (on CP4D 5.1) do not properly limit the allocation of system resources. An authenticated user with internal knowledge of the environment could exploit this weakness to cause a denial of service.

References

Community reviews

Loading reviews…