# CVE-2023-50707: Uncontrolled Resource Consumption in EFACEC BCU 500

> An attacker can cause a denial-of-service condition on the EFACEC BCU 500 by sending custom requests during active user sessions.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-29gw-r2hj-fm58

## What is CVE-2023-50707?

CVE-2023-50707 is a critical denial of service vulnerability in EFACEC BCU 500, published on 19 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Through the exploitation of active user sessions, an attacker could send custom requests to cause a denial-of-service condition on the device.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Efacec Bcu 500 Firmware.

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

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

## Is CVE-2023-50707 being exploited?

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

## Other vulnerabilities in EFACEC BCU 500

- [CVE-2023-6689](https://insights.sbomify.com/CVE-2023-6689/): Cross-Site Request Forgery in EFACEC BCU 500 (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50707 is a critical denial of service vulnerability in EFACEC BCU 500, published on 19 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-50707 in the wild and no public exploit code.

Affected product: EFACEC BCU 500. 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-50707/ (Markdown: https://insights.sbomify.com/CVE-2023-50707/index.md)
```

## Sources

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

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