# CVE-2018-6407: Denial of service in n/a

> An unauthenticated attacker can crash Conceptronic IP cameras by sending a POST request with a large body, causing a complete device freeze.

- **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:** 30 Jan 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-f7fp-c97v-2hhh

## What is CVE-2018-6407?

CVE-2018-6407 is a high-severity denial of service vulnerability in n/a, published on 30 Jan 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Conceptronic CIPCAMPTIWL V3 0.61.30.21 devices. An unauthenticated attacker can crash a device by sending a POST request with a huge body size to /hy-cgi/devices.cgi?cmd=searchlandevice. The crash completely freezes the device.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Conceptronic Cipcamptiwl Firmware, Conceptronic Cipcamptiwl Web Firmware.

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

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

## Is CVE-2018-6407 being exploited?

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

Public exploit code:

- [CVE-2018-6407 & CVE-2018-6408] Conceptronic IPCam Administration panel CSRF and Denial of Service (github_poc): https://github.com/dreadlocked/ConceptronicIPCam_MultipleVulnerabilities

## Other vulnerabilities in n/a

- [CVE-2018-6408](https://insights.sbomify.com/CVE-2018-6408/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-6407 is a high-severity denial of service vulnerability in n/a, published on 30 Jan 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-6407 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-2018-6407/ (Markdown: https://insights.sbomify.com/CVE-2018-6407/index.md)
```

## Sources

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

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