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

> Attackers can cause denial of service on ASUS HG100 devices by flooding them with IPv4 packets.

- **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:** 10 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mvp7-6w38-76fr

## What is CVE-2018-11492?

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

### Official description

ASUS HG100 devices allow denial of service via an IPv4 packet flood.

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

It affects 1 product.


Products: Asus Hg100 Firmware.

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

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

## Is CVE-2018-11492 being exploited?

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

Public exploit code:

- ASUS HG100 - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2019-11061](https://insights.sbomify.com/CVE-2019-11061/): HG100 has a broken access control vulnerability in its Web API Server (critical 10.0)
- [CVE-2018-11491](https://insights.sbomify.com/CVE-2018-11491/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-11060](https://insights.sbomify.com/CVE-2019-11060/): HG100 contains an Uncontrolled Resource Consumption vulnerability (high 7.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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