# CVE-2002-0812: Hardcoded credentials in n/a

> Remote attackers can read and modify sensitive configuration data on Compaq WL310 access points due to hardcoded default SNMP community strings.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 10 Aug 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-5xq5-3xp2-qp33

## What is CVE-2002-0812?

CVE-2002-0812 is a medium-severity vulnerability in n/a, published on 10 Aug 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Information leak in Compaq WL310, and the Orinoco Residential Gateway access point it is based on, uses a system identification string as a default SNMP read/write community string, which allows remote attackers to obtain and modify sensitive configuration information by querying for the identification string.

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

## Which versions are affected by CVE-2002-0812?

It affects 3 products.


Products: Hpe Compaq Wl310 Firmware, Proxim Orinoco Rg-1000 Firmware, Proxim Orinoco Rg-1100 Firmware.

## How do I fix CVE-2002-0812?

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

## Is CVE-2002-0812 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0812 exists.

Public exploit code:

- Orinoco OEM Residential Gateway - SNMP Community String Remote Configuration (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0812 and fix it if it is affected.

What it is: CVE-2002-0812 is a medium-severity vulnerability in n/a, published on 10 Aug 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0812 exists.

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-2002-0812/ (Markdown: https://insights.sbomify.com/CVE-2002-0812/index.md)
```

## Sources

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

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