# CVE-2018-18287: Information disclosure in n/a

> Remote attackers can view internal hostnames and IP addresses by accessing the login page source code on ASUS RT-AC58U routers.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2rpj-wp8m-5xgx

## What is CVE-2018-18287?

CVE-2018-18287 is a medium-severity vulnerability in n/a, published on 14 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On ASUS RT-AC58U 3.0.0.4.380_6516 devices, remote attackers can discover hostnames and IP addresses by reading dhcpLeaseInfo data in the HTML source code of the Main_Login.asp page.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Asus Rt-Ac58u Firmware.

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

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

## Is CVE-2018-18287 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18291](https://insights.sbomify.com/CVE-2018-18291/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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