# CVE-2006-0248: Information disclosure in n/a

> Remote attackers can access privileged user lists and configuration settings via direct HTTP requests on affected routers.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** 18 Jan 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wpwj-mgxf-qrhp

## What is CVE-2006-0248?

CVE-2006-0248 is a medium-severity vulnerability in n/a, published on 18 Jan 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Virata-EmWeb web server 6_1_0, as used in (1) Intracom JetSpeed 500 and 520 and (2) Allied Data Technologies CopperJet 811 RouterPlus, allows remote attackers to access privileged information, such as user lists and configuration settings, via direct HTTP requests.

## Which versions are affected by CVE-2006-0248?

It affects 1 product.


Products: Intracom Jetspeed.

## How do I fix CVE-2006-0248?

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

## Is CVE-2006-0248 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0248 and fix it if it is affected.

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

## Sources

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

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