# CVE-2024-52547: Lorex 2K Indoor Wi-Fi Security Camera - Stack buffer overflow

> An authenticated attacker can trigger a stack buffer overflow in the camera's DHIP service, potentially allowing remote code execution.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Dec 2024
- **Updated:** 5 Sep 2025
- **Also known as:** GHSA-qf6v-j5x7-cg97

## What is CVE-2024-52547?

CVE-2024-52547 is a high-severity memory corruption vulnerability in Lorex 2K Indoor Wi-Fi Security Camera, published on 3 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An authenticated attacker can trigger a stack based buffer overflow in the DHIP Service (TCP port 80). This vulnerability has been resolved in firmware version 2.800.0000000.8.R.20241111.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2024-52547 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52547 is a high-severity memory corruption vulnerability in Lorex 2K Indoor Wi-Fi Security Camera, published on 3 Dec 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52547 exists.

Affected product: Lorex 2K Indoor Wi-Fi Security Camera. 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-52547/ (Markdown: https://insights.sbomify.com/CVE-2024-52547/index.md)
```

## Sources

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

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