Skip to main content
CVE-2024-49350VulnerabilityPublished

CVE-2024-49350: IBM Db2 for Linux, UNIX and Windows · Stack-based Buffer Overflow

Affects IBM Db2 for Linux, UNIX and WindowsSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 May 2025

  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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
IBM Db2 for Linux, UNIX and WindowsAffected
  • =11.5.0
  • =12.1.0
  • =11.1.0
Fixed in–

AI-suggested

Given the absence of publicly available patches at this time, European organizations should implement several specific mitigation strategies beyond generic advice: 1) Restrict network access to IBM Db2 servers to trusted hosts and networks using firewalls and network segmentation to reduce exposure to potentially malicious queries. 2) Enforce strict access controls and monitor database user privileges to minimize the number of accounts with the ability to send queries, especially those with low privilege levels that can still trigger the vulnerability. 3) Deploy database activity monitoring tools to detect anomalous or malformed query patterns that could indicate exploitation attempts. 4) Implement robust logging and alerting mechanisms to quickly identify and respond to database crashes or unusual behavior. 5) Prepare incident response plans specifically addressing database availability incidents, including failover and recovery procedures to minimize downtime. 6) Engage with IBM support channels to obtain patches or workarounds as soon as they become available and prioritize timely deployment in test and production environments. 7) Consider temporary use of query filtering or input validation proxies if feasible to block suspicious queries. These targeted measures will help reduce the attack surface and improve detection and response capabilities until official fixes are released.

Description

IBM Db2 for Linux, UNIX and Windows (includes DB2 Connect Server) 11.1.0 through 11.1.4.7, 11.5.0 through 11.5.9 and 12.1.0 through 12.1.1 is vulnerable to a denial of service as the server may crash under certain conditions with a specially crafted query.

References

Community reviews

Loading reviews…