CVE-2024-30917: Fast-DDS · n/a
Affects Fast-DDSSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Apr 2024
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-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubeprosima/Fast-DDSpkg:github/eprosima/Fast-DDSOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-30917, organizations should first identify all deployments of eProsima FastDDS version 2.14.0 or earlier within their environments. Restrict local access to systems running FastDDS to trusted users and processes only, minimizing the risk of local exploitation. Implement strict access controls and user privilege management to prevent unauthorized local access. Monitor system logs and application behavior for signs of abnormal crashes or resource exhaustion related to the DurabilityService QoS component. Where possible, apply runtime protections such as sandboxing or containerization to isolate FastDDS processes and limit the impact of potential DoS attacks. Engage with eProsima or the FastDDS community to track the release of patches or updates addressing this vulnerability and plan timely upgrades. Additionally, conduct code reviews or static analysis on custom configurations or extensions involving the history_depth parameter to ensure proper validation and handling. Consider implementing network segmentation and endpoint security controls to reduce the attack surface and detect anomalous local activity. Finally, prepare incident response plans that include scenarios involving FastDDS service disruptions.
Description
An issue was discovered in eProsima FastDDS v.2.14.0 and before, allows a local attacker to cause a denial of service (DoS) and obtain sensitive information via a crafted history_depth parameter in DurabilityService QoS component.