CVE-2024-10838
Memory Safety in Eclipse Cyclone Data Distribution Service ≤ 0.10.5
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-10838 is a high-severity Wrap or Wraparound (CWE-191) vulnerability in Eclipse Cyclone Data Distribution Service. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique LSASS Memory (T1003.001); ranked in the top 40% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-10838, published on 2025-03-12, is an integer underflow vulnerability (CWE-191) affecting Eclipse CycloneDDS. The flaw occurs during deserialization and enables out-of-bounds reads of heap memory, potentially incorporating secret data or pointers that reveal the address space layout into deserialized data structures.
Any unauthenticated attacker can exploit this vulnerability remotely over the network with low attack complexity, as indicated by its CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H). Successful exploitation may leak sensitive information via confidentiality impacts or trigger thread crashes and denial-of-service conditions through availability impacts.
Advisories and patches are detailed in Eclipse CycloneDDS resources, including the GitHub security advisory (GHSA-6jj6-w25p-jc42) and release tag 0.10.5, with CVE assignment tracked at Eclipse GitLab issue 46. Security practitioners should review these for mitigation guidance, such as updating to the patched version.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-54131
Vulnerability Data
An integer underflow during deserialization may allow any unauthenticated user to read out of bounds heap memory. This may result into secret data or pointers revealing the layout of the address space to be included into a deserialized data structure,…
more
which may potentially lead to thread crashes or cause denial of service conditions.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static/dynamic analysis directly find integer underflow defects before code is released.
Security engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer underflow during subtraction.
Input validation can reject or sanitize values that would cause a subtraction to underflow the representable range.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Vulnerability scanning and code analysis can surface underflow flaws after they are introduced.
Routine patching can remediate known underflow bugs once they are discovered in deployed software.
Secure SDLC practices directly prevent integer underflow defects via input validation, bounds checking, and static analysis.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.