# CVE-2018-6413: Memory corruption in DS-2CD9111-S

> Remote attackers can cause a denial of service on Hikvision cameras via a crafted network setting request due to a buffer overflow.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 18 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5wjc-c32v-25gw

## What is CVE-2018-6413?

CVE-2018-6413 is a high-severity memory corruption vulnerability in hikvision DS-2CD9111-S, published on 18 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a buffer overflow in the Hikvision Camera DS-2CD9111-S of V4.1.2 build 160203 and before, and this vulnerability allows remote attackers to launch a denial of service attack (service interruption) via a crafted network setting interface request.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2018-6413?

It affects 1 product.


Products: Hikvision Ds-2cd9111-S Firmware.

## How do I fix CVE-2018-6413?

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

## Is CVE-2018-6413 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6413 and fix it if it is affected.

What it is: CVE-2018-6413 is a high-severity memory corruption vulnerability in hikvision DS-2CD9111-S, published on 18 Apr 2018. 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-2018-6413 in the wild and no public exploit code.

Affected product: hikvision DS-2CD9111-S. 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-2018-6413/ (Markdown: https://insights.sbomify.com/CVE-2018-6413/index.md)
```

## Sources

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

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