# CVE-2017-5632: Denial of service in n/a

> A local attacker can crash the WAN connection of an ASUS router by sending a specific Nmap command, causing a denial of service.

- **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:** 30 Jan 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pqc4-j887-3v8j

## What is CVE-2017-5632?

CVE-2017-5632 is a medium-severity denial of service vulnerability in n/a, published on 30 Jan 2017. 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 the ASUS RT-N56U Wireless Router with Firmware 3.0.0.4.374_979. When executing an "nmap -O" command that specifies an IP address of an affected device, one can crash the device's WAN connection, causing disconnection from the Internet, a Denial of Service (DoS). The attack is only possible from within the local area network.

## Which versions are affected by CVE-2017-5632?

It affects 1 product.


Products: Asus Rt-N56u Firmware.

## How do I fix CVE-2017-5632?

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

## Is CVE-2017-5632 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5632 and fix it if it is affected.

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

## Sources

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

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