# CVE-2007-5420: Information disclosure in n/a

> Remote attackers can obtain router existence and product details when remote management is disabled but a web server is configured.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8vqq-grj6-7fxj

## What is CVE-2007-5420?

CVE-2007-5420 is a low-severity vulnerability in n/a, published on 12 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 3Com 3CRWER100-75 router with 1.2.10ww software, when remote management is disabled but a web server has been configured, serves a web page to external clients, which might allow remote attackers to obtain information about the router's existence and product details.

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

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

It affects 1 product.


Products: 3com 3crwe554g72t.

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

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

## Is CVE-2007-5420 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-5419](https://insights.sbomify.com/CVE-2007-5419/): Misconfiguration in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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