# CVE-2023-50257: Disconnect Vulnerability in RTPS Packets Used by SROS2

> Attackers can forcibly disconnect subscribers and prevent new connections in SROS2-enabled Fast DDS applications by sending unencrypted RTPS packets.

- **Severity:** Critical 9.7 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Feb 2024
- **Updated:** 14 Aug 2024
- **Also known as:** DEBIAN-CVE-2023-50257, GHSA-v5r6-8mvh-cp98, UBUNTU-CVE-2023-50257

## What is CVE-2023-50257?

CVE-2023-50257 is a critical denial of service vulnerability in eProsima Fast-DDS, published on 19 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

eProsima Fast DDS (formerly Fast RTPS) is a C++ implementation of the Data Distribution Service standard of the Object Management Group. Even with the application of SROS2, due to the issue where the data (`p[UD]`) and `guid` values used to disconnect between nodes are not encrypted, a vulnerability has been discovered where a malicious attacker can forcibly disconnect a Subscriber and can deny a Subscriber attempting to connect. Afterwards, if the attacker sends the packet for disconnecting, which is data (`p[UD]`), to the Global Data Space (`239.255.0.1:7400`) using the said Publisher ID, all the Subscribers (Listeners) connected to the Publisher (Talker) will not receive any data and their connection will be disconnected. Moreover, if this disconnection packet is sent continuously, the Subscribers (Listeners) trying to connect will not be able to do so. Since the initial commit of the `SecurityManager.cpp` code (`init`, `on_process_handshake`) on Nov 8, 2016, the Disconnect Vulnerability in RTPS Packets Used by SROS2 has been present prior to versions 2.13.0, 2.12.2, 2.11.3, 2.10.3, and 2.6.7.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2023-50257?

It affects 1 product.


Products: Eprosima Fast Dds.

## How do I fix CVE-2023-50257?

Upgrade to a fixed version.

## Is CVE-2023-50257 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50257 exists.

Public exploit code:

- This repository is for research purposes (2025 Sejong Univ. Capstone Design) (github_poc): https://github.com/Jminis/CVE-2023-50257

## Other vulnerabilities in eProsima Fast-DDS

- [CVE-2025-67108](https://insights.sbomify.com/CVE-2025-67108/): Security feature bypass in n/a (critical 10.0)
- [CVE-2024-28231](https://insights.sbomify.com/CVE-2024-28231/): Manipulated DATA Submessage causes a heap-buffer-overflow error (critical 9.7)
- [CVE-2023-50716](https://insights.sbomify.com/CVE-2023-50716/): Invalid DATA_FRAG Submessage causes a bad-free error (critical 9.7)
- [CVE-2023-42459](https://insights.sbomify.com/CVE-2023-42459/): Malformed DATA submessage leads to bad-free error in Fast-DDS (high 8.6)
- [CVE-2024-30258](https://insights.sbomify.com/CVE-2024-30258/): FastDDS crash when publisher send malformed packet (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-50257 and fix it if it is affected.

What it is: CVE-2023-50257 is a critical denial of service vulnerability in eProsima Fast-DDS, published on 19 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50257 exists.

Affected product: eProsima Fast-DDS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-50257/ (Markdown: https://insights.sbomify.com/CVE-2023-50257/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-50257
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-50257
- OSV: https://osv.dev/vulnerability/CVE-2023-50257

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-50257/
Summaries are generated and may contain mistakes; the official description above is the record.