# CVE-2024-41623: Code injection in n/a

> A local attacker can execute arbitrary code on D3D IP Cameras via a crafted payload, posing a risk to physical security systems.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 13 Aug 2024
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-4wrj-qhhf-3c55

## What is CVE-2024-41623?

CVE-2024-41623 is a critical code injection vulnerability in n/a, published on 13 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in D3D Security D3D IP Camera (D8801) v.V9.1.17.1.4-20180428 allows a local attacker to execute arbitrary code via a crafted payload

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: D3dsecurity D8801 Firmware.

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

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

## Is CVE-2024-41623 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41623 is a critical code injection vulnerability in n/a, published on 13 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41623 in the wild and no public exploit code.

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

## Sources

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

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