# CVE-2024-52548: Lorex 2K Indoor Wi-Fi Security Camera - Code signing bypass

> Attackers with command execution can bypass kernel code signing to run arbitrary native code on Lorex security cameras.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Dec 2024
- **Updated:** 3 Dec 2024
- **Also known as:** GHSA-fp87-jfrm-4f3f

## What is CVE-2024-52548?

CVE-2024-52548 is a medium-severity vulnerability in Lorex 2K Indoor Wi-Fi Security Camera, published on 3 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An attacker who can execute arbitrary Operating Systems commands, can bypass code signing enforcements in the kernel, and execute arbitrary native code. This vulnerability has been resolved in firmware version 2.800.0000000.8.R.20241111.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2024-52548 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52548 is a medium-severity vulnerability in Lorex 2K Indoor Wi-Fi Security Camera, published on 3 Dec 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-52548 in the wild and no public exploit code.

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-52548/ (Markdown: https://insights.sbomify.com/CVE-2024-52548/index.md)
```

## Sources

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

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