# CVE-2024-5949: Deep Sea Electronics DSE855 Multipart Boundary Infinite Loop Denial-of-Service Vulnerability

> Network-adjacent attackers can cause a denial-of-service condition on Deep Sea Electronics DSE855 devices via an infinite loop in multipart boundary handling.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-hp7j-wvg8-rgv3

## What is CVE-2024-5949?

CVE-2024-5949 is a medium-severity denial of service vulnerability in Deep Sea Electronics DSE855, published on 13 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Deep Sea Electronics DSE855 Multipart Boundary Infinite Loop Denial-of-Service Vulnerability. This vulnerability allows network-adjacent attackers to create a denial-of-service condition on affected installations of Deep Sea Electronics DSE855 devices. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the handling of multipart boundaries. The issue results from a logic error that can lead to an infinite loop. An attacker can leverage this vulnerability to create a denial-of-service condition on the system. Was ZDI-CAN-23171.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

## Which versions are affected by CVE-2024-5949?

It affects 1 product.


Products: Deepseaelectronics Dse855 Firmware.

## How do I fix CVE-2024-5949?

No fix has been published for CVE-2024-5949 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-5949 being exploited?

There is no known exploitation of CVE-2024-5949 in the wild and no public exploit code.

## Other vulnerabilities in Deep Sea Electronics DSE855

- [CVE-2024-5948](https://insights.sbomify.com/CVE-2024-5948/): Deep Sea Electronics DSE855 Multipart Boundary Stack-Based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2024-5950](https://insights.sbomify.com/CVE-2024-5950/): Deep Sea Electronics DSE855 Multipart Value Handling Stack-Based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2024-5951](https://insights.sbomify.com/CVE-2024-5951/): Deep Sea Electronics DSE855 Factory Reset Missing Authentication Denial-of-Service Vulnerability (high 7.1)
- [CVE-2024-5947](https://insights.sbomify.com/CVE-2024-5947/): Deep Sea Electronics DSE855 Configuration Backup Missing Authentication Information Disclosure Vulnerability (medium 6.5)
- [CVE-2024-5952](https://insights.sbomify.com/CVE-2024-5952/): Deep Sea Electronics DSE855 Restart Missing Authentication Denial-of-Service Vulnerability (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5949 and fix it if it is affected.

What it is: CVE-2024-5949 is a medium-severity denial of service vulnerability in Deep Sea Electronics DSE855, published on 13 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5949 in the wild and no public exploit code.

Affected product: Deep Sea Electronics DSE855. 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-2024-5949/ (Markdown: https://insights.sbomify.com/CVE-2024-5949/index.md)
```

## Sources

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

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