Cloudanix VulnDB

CVE-2024-30917

Medium · 5.5

CVSS

5.5

EPSS

0.2%

Published

Apr 11, 2024

CISA due date

—

Cloudanix analysis

Monitor only SSVC: Track

A bug in data-sharing software can let someone on the same computer crash the program or peek at internal details by feeding it bad settings.

Exploitation
Local Privilege
Attacker needs
Low Privilege
Complexity
Low
Impact
Denial Of Service
Component
Library
Class
Improper Input Validation
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Insufficient validation of the history_depth parameter in the DurabilityService QoS component permits crafted values to trigger resource exhaustion resulting in denial of service or unintended exposure of internal state.

Why it matters to the business

Systems using this middleware for distributed real-time data exchange may suffer unexpected outages or leakage of configuration details, disrupting operations in robotics, autonomous vehicles, or industrial control environments.

How an attack unfolds

An attacker with local access supplies a maliciously formatted history_depth value when configuring the DurabilityService QoS; the library fails to sanitize the input, causing the service to allocate excessive resources or leak memory contents.

How to fix it

Upgrade eProsima FastDDS to a version that enforces proper bounds checking on history_depth and other QoS parameters; until a fix is released, restrict local configuration privileges and validate QoS settings before use.

How to confirm the fix worked

Review source or binary for input sanitization on history_depth in DurabilityService initialization; test with extreme and negative values to confirm rejection without crash or leakage.

Typical attack path

  1. Obtain local access to a host running the vulnerable middleware
  2. Identify an application or service that initializes DurabilityService QoS
  3. Craft and inject a malformed history_depth parameter into the QoS policy
  4. Trigger initialization or reconfiguration to induce DoS or data exposure

How to detect it

Examine application logs for unexpected crashes or memory errors during QoS initialization; correlate with local user activity that modifies DurabilityService configuration files or API calls.

What your security team should do

  • Monitor vendor advisories for an official patched release and schedule upgrade
  • Apply least-privilege controls on processes that load QoS configurations
  • Add runtime bounds checks or wrappers around DurabilityService setup where feasible

The record

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.

Affected packages

Ecosystem Package Introduced Fixed
Debian:11 fastdds 0 No fix
Debian:12 fastdds 0 No fix
Debian:13 fastdds 0 2.14.1+ds-1
Ubuntu:22.04:LTS fastdds 0 No fix
Ubuntu:24.04:LTS fastdds 0 No fix
Ubuntu:24.10 fastdds 0 No fix
Ubuntu:25.04 fastdds 0 No fix
Ubuntu:25.10 fastdds 0 No fix
Ubuntu:Pro:22.04:LTS fastdds 0 No fix

Related vulnerabilities