# CVE-2007-0877: Denial of service in n/a

> Attackers can cause a denial of service on March Networks DVRs, impacting video surveillance availability.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 12 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m5v3-cc3w-4463

## What is CVE-2007-0877?

CVE-2007-0877 is a medium-severity denial of service vulnerability in n/a, published on 12 Feb 2007. 

### Official description

Unspecified vulnerability in March Networks DVR 3000 and 4000 Digital Video Recorders allows attackers to cause an unspecified denial of service.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

## Which versions are affected by CVE-2007-0877?

It affects 5 products.


Products: March Networks 3108 Dvr, March Networks 3204 Dvr, March Networks 4210 Dvr, March Networks 4310 Dvr, March Networks 4410 Dvr.

## How do I fix CVE-2007-0877?

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

## Is CVE-2007-0877 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0877 and fix it if it is affected.

What it is: CVE-2007-0877 is a medium-severity denial of service vulnerability in n/a, published on 12 Feb 2007. 
Exploitation: There is no known exploitation of CVE-2007-0877 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-2007-0877/ (Markdown: https://insights.sbomify.com/CVE-2007-0877/index.md)
```

## Sources

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

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