CVE-2024-39724
Resource Exhaustion Vulnerability in IBM Db2 Big SQL Causing DoS
Publication date: 2026-02-04
Last updated on: 2026-02-04
Assigner: IBM Corporation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ibm | db2_big_sql | 7.6 |
| ibm | db2_big_sql | 7.7 |
| ibm | db2_big_sql | to 5.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-770 | The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There is no specific information provided about detection methods or commands to identify this vulnerability on your network or system.
Can you explain this vulnerability to me?
CVE-2024-39724 is a vulnerability in IBM Db2 Big SQL on Cloud Pak for Data versions 7.8 and earlier. It occurs because the system does not properly limit resource allocation due to a lack of throttling on an API.
This flaw allows an authenticated user who has internal knowledge of the system to cause a denial of service (DoS) by exhausting system resources.
The vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an authenticated user with some internal knowledge to cause a denial of service (DoS) condition.
The attacker can exhaust system resources, making the affected IBM Db2 Big SQL service unavailable or degraded, which impacts availability.
There is no impact on confidentiality or integrity, but the availability of the service is highly affected.
What immediate steps should I take to mitigate this vulnerability?
The recommended immediate step to mitigate this vulnerability is to upgrade IBM Db2 Big SQL to version 8.2 or later, which is available on Cloud Pak for Data 5.2 or later.
No workarounds or other mitigations are provided, so upgrading is the primary remediation.
It is also advised to assess the impact of this vulnerability in your environment.