CVE-2024-39750: IBM Analytics Content Hub · Classic Buffer Overflow
Affects IBM Analytics Content HubSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% 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:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBM Analytics Content Hub | Affected
| Fixed in– |
AI-suggested
Given the absence of an official patch at the time of this report, European organizations should implement the following specific mitigations: 1) Restrict and monitor access to IBM Analytics Content Hub to only trusted and necessary users, enforcing strong authentication mechanisms such as multi-factor authentication (MFA) to reduce the risk of credential compromise. 2) Employ network segmentation and firewall rules to limit exposure of the Analytics Content Hub servers to only essential internal networks and trusted IP ranges. 3) Conduct thorough logging and monitoring of user activities and system behavior to detect anomalous actions that could indicate exploitation attempts, including unusual buffer overflow indicators or crashes. 4) Prepare incident response plans specifically addressing potential exploitation scenarios of this vulnerability, including rapid isolation and forensic analysis. 5) Engage with IBM support channels to obtain patches or workarounds as soon as they become available and prioritize timely deployment. 6) Consider deploying application-layer protections such as Web Application Firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting buffer overflow vectors. 7) Regularly audit and update user privileges to minimize the number of users with authenticated access to the vulnerable system.
Description
IBM Analytics Content Hub 2.0 is vulnerable to a buffer overflow due to improper return length checking. A remote authenticated attacker could overflow a buffer and execute arbitrary code on the system or cause the server to crash.