DJI Mavic 3 Pro Service Port 10000 libv2_sdk.so my_tcp_receive out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in DJI Mavic 3 Pro, Mavic 3, Mavic 3 Classic, Mavic 3 Enterprise, Matrice 300, Matrice M30 and Mini 3 Pro and classified as critical. Affected by this vulnerability is the function my_tcp_receive of the file libv2_sdk.so of the component Service Port 10000. Performing a manipulation results in out-of-bounds write.
This vulnerability is reported as CVE-2023-51454. The attacker must have access to the local network to execute the attack. No exploit exists.
The affected component should be upgraded.
Details
A vulnerability was found in DJI Mavic 3 Pro, Mavic 3, Mavic 3 Classic, Mavic 3 Enterprise, Matrice 300, Matrice M30 and Mini 3 Pro. It has been classified as critical. This affects the function my_tcp_receive of the file libv2_sdk.so of the component Service Port 10000. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. CWE is classifying the issue as CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
A Out-of-bounds Write issue affecting the v2_sdk_service running on a set of DJI drone devices on the port 10000 could allow an attacker to overwrite a pointer in the process memory through a crafted payload triggering an unsafe memory write operation in the my_tcp_receive function implemented in the libv2_sdk.so library used by the dji_vtwo_sdk binary implementing the service, potentially leading to a memory information leak or to an arbitrary code execution. Affected models are Mavic 3 Pro until v01.01.0300, Mavic 3 until v01.00.1200, Mavic 3 Classic until v01.00.0500, Mavic 3 Enterprise until v07.01.10.03, Matrice 300 until v57.00.01.00, Matrice M30 until v07.01.0022 and Mini 3 Pro until v01.00.0620.
The weakness was disclosed by Diego Giubertoni. The advisory is shared at nozominetworks.com. This vulnerability is uniquely identified as CVE-2023-51454 since 12/19/2023. The exploitability is told to be difficult. The attack needs to be done within the local network. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.6
VulDB Base Score: 6.8
VulDB Temp Score: 6.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.8
CNA Vector (Nozomi Networks Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Out-of-bounds writeCWE: CWE-787 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
12/19/2023 🔍04/02/2024 🔍
04/02/2024 🔍
04/09/2025 🔍
Sources
Advisory: nozominetworks.comResearcher: Diego Giubertoni
Status: Confirmed
CVE: CVE-2023-51454 (🔍)
GCVE (CVE): GCVE-0-2023-51454
GCVE (VulDB): GCVE-100-259017
Entry
Created: 04/02/2024 13:02Updated: 04/09/2025 11:36
Changes: 04/02/2024 13:02 (66), 05/08/2024 17:47 (1), 04/09/2025 11:36 (4)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.