# CVE-2023-50685: Denial of service in n/a

> A remote attacker can cause a denial of service in Hipcam Cameras RealServer by sending a crafted script to the client_port parameter.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2024
- **Updated:** 16 Aug 2024
- **Also known as:** GHSA-wmxf-vfxg-wrm4

## What is CVE-2023-50685?

CVE-2023-50685 is a high-severity denial of service vulnerability in n/a, published on 2 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Hipcam Cameras RealServer v.1.0 allows a remote attacker to cause a denial of service via a crafted script to the client_port parameter.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2023-50685 being exploited?

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

Public exploit code:

- This POC exploits a format validation vulnerability in the RTSP service of the Hipcam RealServer/V1.0, inducing a crash for approximately 45 seconds by injecting random data into the 'client_port' parameter during the RTSP SETUP request. Hipcam RealServer/V1.0 is used in many Hipcam Cameras. | CVE-2023-50685 (github_poc): https://github.com/MaximilianLJungblut/Hipcam-RTSP-Format-Validation-Vulnerability

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50685 is a high-severity denial of service vulnerability in n/a, published on 2 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-50685 exists.

Affected product: n/a. 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-50685/ (Markdown: https://insights.sbomify.com/CVE-2023-50685/index.md)
```

## Sources

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

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