# CVE-2024-29948: Memory corruption in DS-7604NXI-K1/4P

> An authenticated attacker can cause service abnormality in Hikvision NVRs via out-of-bounds read, requiring vendor patches.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2024
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-5w4g-hwj9-f75w

## What is CVE-2024-29948?

CVE-2024-29948 is a low-severity memory corruption vulnerability in Hikvision DS-7604NXI-K1/4P, published on 2 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

There is an out-of-bounds read vulnerability in some Hikvision NVRs. An authenticated attacker could exploit this vulnerability by sending specially crafted messages to a vulnerable device, causing a service abnormality.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2024-29948 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29948 is a low-severity memory corruption vulnerability in Hikvision DS-7604NXI-K1/4P, published on 2 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-29948 in the wild and no public exploit code.

Affected product: Hikvision DS-7604NXI-K1/4P. 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-29948/ (Markdown: https://insights.sbomify.com/CVE-2024-29948/index.md)
```

## Sources

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

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