# CVE-2019-11878: Integer overflow in n/a

> A local attacker can crash the IP camera for approximately two minutes by sending a crafted message with an oversized size field.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4gcx-xcfm-vwwv

## What is CVE-2019-11878?

CVE-2019-11878 is a medium-severity vulnerability in n/a, published on 10 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on XiongMai Besder IP20H1 V4.02.R12.00035520.12012.047500.00200 cameras. An attacker on the same local network as the camera can craft a message with a size field larger than 0x80000000 and send it to the camera, related to an integer overflow or use of a negative number. This then crashes the camera for about 120 seconds.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2019-11878?

It affects 1 product.


Products: Xiongmaitech Besder Ip20h1 Firmware.

## How do I fix CVE-2019-11878?

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

## Is CVE-2019-11878 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11878 and fix it if it is affected.

What it is: CVE-2019-11878 is a medium-severity vulnerability in n/a, published on 10 May 2019. 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-2019-11878 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-2019-11878/ (Markdown: https://insights.sbomify.com/CVE-2019-11878/index.md)
```

## Sources

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

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