dbcve.org
Compaq Wl310 FirmwareOperating system · Hpe

CVE-2002-0812

MEDIUM · 6.4 CVSS v2.0 Published 2002-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Compaq WL310 and Orinoco Residential Gateway access points use the system identification string as the default SNMP read/write community string. Since this identifier is discoverable through SNMP queries, remote attackers can use it to read and modify sensitive configuration data on the affected devices.

MitigationChange the default SNMP community strings to unique, strong values immediately. If SNMP is not required, disable it entirely; otherwise ensure community strings differ from the system identification and implement SNMP access controls to limit which hosts can query the device.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Compaq Wl310 FirmwareOperating system
Affected:all versions
Orinoco Rg 1000 FirmwareOperating system
Affected:all versions
Orinoco Rg 1100 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:P/I:P/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model and firmware
    Identify the exact model and firmware version of the access point. For Compaq WL310, Proxim Orinoco RG 1000, or RG 1100, check the device's web interface status page, SNMP sysDescr OID (1.3.6.1.2.1.1.1), or console interface.
    Affected if The device is a Compaq WL310, Proxim Orinoco RG 1000, or Proxim Orinoco RG 1100 with any firmware version.
  2. Verify SNMP is enabled
    Query the device using SNMP GET on snmpEnable (1.3.6.1.4.1.11.2.14.11.5.1.1.2) or check via the device web interface under SNMP settings. Alternatively, send an SNMP request to the device with any community string.
    Affected if SNMP is enabled and responding to queries on the device.
  3. Retrieve configured SNMP community strings
    Perform an SNMP walk or GET on the community strings OID (1.3.6.1.6.3.12.1.5.1.2 or snmpCommunityName). If read-write access exists, query snmpTargetAddrTCommunity or check the device SNMP configuration page.
    Affected if SNMP community strings are configured and accessible via SNMP query or device management interface.
  4. Retrieve system identification string
    Query the SNMP sysDescr (1.3.6.1.2.1.1.1) or sysName (1.3.6.1.2.1.1.5) OID. Alternatively, check the device status page or label which displays the system identification.
    Affected if A system identification string is present on the device.
  5. Compare community string to system identification
    Extract the configured read-write SNMP community string from step 3 and compare it exactly to the system identification string from step 4. Note whether they are identical.
    Affected if The SNMP read-write community string exactly matches the device system identification string.

The device is affected if it is a Compaq WL310, Orinoco RG 1000, or RG 1100 with SNMP enabled and the configured SNMP read-write community string matches the system identification string.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Change the default SNMP community strings to unique, strong values immediately. If SNMP is not required, disable it entirely; otherwise ensure community strings differ from the system identification and implement SNMP access controls to limit which hosts can query the device.

Fix this in Compaq Wl310 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2002-0812 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2002-0812 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data