dbcve.org
Tsunami Mp.11 2411Hardware / appliance · Proxim

CVE-2008-5866

HIGH · 10.0 CVSS v2.0 Published 2009-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The Proxim Wireless Tsunami MP.11 2411 with firmware 3.0.3 has public as its default SNMP read/write community, which makes it easier for remote attackers to obtain sensitive information or modify SNMP variables.

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 Proxim Wireless Tsunami MP.11 2411 with firmware 3.0.3 ships with 'public' as the default SNMP read/write community string, allowing any remote attacker to authenticate to SNMP and read or modify SNMP variables including sensitive system information.

MitigationChange the default SNMP community strings to unique, complex values, disable SNMP if not required, or restrict SNMP access to authorized management stations via ACLs.

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
Tsunami Mp.11 2411Hardware / appliance
Affected:= 3.0.3

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
Complete
Integrity
Complete
Availability
Complete

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

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. Identify the device model
    Access the device's web interface, CLI, or SNMP interface and verify the model is Proxim Tsunami MP.11 2411. This can be done via SNMP query (snmpwalk on OID like sysDescr) or by checking the device's administrative interface for model information.
    Affected if The device is NOT a Proxim Tsunami MP.11 2411 - this CVE does not apply to other models.
  2. Check the firmware version
    Access the device's administrative interface (web or CLI) and locate the firmware version information, typically found in the System Info or Status page. Alternatively, query SNMP OID 1.3.6.1.2.1.47.1.1.1.1.9.1 (entPhysicalSoftwareRev) if available.
    Affected if The firmware version is NOT exactly 3.0.3 - only version 3.0.3 is affected by this CVE.
  3. Verify SNMP is enabled
    Check the device's configuration to confirm SNMP service is enabled. This is typically found in the SNMP/Management settings of the device's web interface, or by attempting an SNMP query to the device. If SNMP queries return responses, it is enabled.
    Affected if SNMP is disabled on the device - the vulnerability cannot be exploited if SNMP is not running.
  4. Inspect the SNMP community string configuration
    Query the device using snmpwalk with community string 'public' (e.g., snmpwalk -v2c -c public <device_ip>) or access the SNMP configuration page in the device's web interface to view the configured read/write community string.
    Affected if The configured SNMP read/write community string is 'public' - this is the default vulnerable value. If a different community string is set, the device is not affected by this specific CVE.

The environment is affected only if the device is a Proxim Tsunami MP.11 2411 running firmware version 3.0.3 with SNMP enabled and the default community string 'public' still configured.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Change the default SNMP community strings to unique, complex values, disable SNMP if not required, or restrict SNMP access to authorized management stations via ACLs.

Recommended fix Moderate confidence
  1. Log into the Tsunami MP.11 2411 administration interface
  2. Navigate to the SNMP configuration settings
  3. Change the default SNMP read/write community string from 'public' to a strong, unique community string (use a complex alphanumeric string of at least 12 characters)
  4. Apply the configuration changes
  5. Verify the new SNMP community string is working correctly
  6. Document the new community string in a secure password manager
  7. Ensure any firewall rules restrict SNMP access (UDP port 161) to authorized management stations only

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tsunami Mp.11 2411 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-5866 — 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-2008-5866 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