# CVE-2013-4776: Denial of service in n/a

> Remote attackers can cause a denial of service on NETGEAR ProSafe switches by sending a crafted HTTP request to the filesystem endpoint.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m83j-f6m7-q446

## What is CVE-2013-4776?

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

### Official description

NETGEAR ProSafe GS724Tv3 and GS716Tv2 with firmware 5.4.1.13 and earlier, GS748Tv4 5.4.1.14, and GS510TP 5.0.4.4 allows remote attackers to cause a denial of service (reboot or crash) via a crafted HTTP request to filesystem/.

## Which versions are affected by CVE-2013-4776?

It affects 5 products.


Products: Netgear Prosafe Firmware, Netgear Prosafe Gs510tp, Netgear Prosafe Gs724t, Netgear Prosafe Gs748t, Netgear Prosafe S716t.

## How do I fix CVE-2013-4776?

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

## Is CVE-2013-4776 being exploited?

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

Public exploit code:

- Netgear ProSafe - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-4775](https://insights.sbomify.com/CVE-2013-4775/): Information disclosure in n/a (high 7.8)
- [CVE-2014-4864](https://insights.sbomify.com/CVE-2014-4864/): Information disclosure in n/a (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4776 and fix it if it is affected.

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

## Sources

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

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