dbcve.org
Unified Wireless Network Solution SoftwareOperating system · Cisco

CVE-2010-2976

HIGH · 10.0 CVSS v2.0 Published 2010-08-10
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 controller in Cisco Unified Wireless Network (UWN) Solution 7.x through 7.0.98.0 has (1) a default SNMP read-only community of public, (2) a default SNMP read-write community of private, and a value of "default" for the (3) SNMP v3 username, (4) SNMP v3 authentication password, and (5) SNMP v3 privacy password, which makes it easier for remote attackers to obtain access.

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 Cisco Unified Wireless Network Solution controller versions 7.x through 7.0.98.0 ships with hardcoded default SNMP credentials: read-only community 'public', read-write community 'private', and default SNMPv3 username/password/privacy values all set to 'default'. This allows unauthenticated remote attackers to gain full administrative access to the wireless controller via SNMP.

MitigationImmediately change all default SNMP community strings and SNMPv3 credentials to unique, strong values; disable default SNMP accounts if not needed; restrict SNMP access to management networks 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
Unified Wireless Network Solution SoftwareOperating system
Affected:= 7.0= 7.0.98.0

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 Cisco Wireless LAN Controller model and software version
    Access the controller CLI via console/SSH and run 'show version' or check the web interface System > General page to view the software version number
    Affected if Software version is 7.0.x or 7.0.98.0 (or any 7.0.x version within the 7.0 through 7.0.98.0 range)
  2. Verify SNMP read-only community string configuration
    Run 'show snmp community' in the controller CLI or check SNMP > v2c in the web interface to see configured community names
    Affected if The read-only community string is set to 'public' (the default) or any well-known value
  3. Verify SNMP read-write community string configuration
    Run 'show snmp community' in the controller CLI or check SNMP > v2c in the web interface to see which community has read-write access
    Affected if The read-write community string is set to 'private' (the default) or any well-known value
  4. Verify SNMPv3 user configuration
    Run 'show snmpv3 user' in the controller CLI or check SNMP > v3 in the web interface to list configured SNMPv3 users
    Affected if An SNMPv3 user exists with username 'default' and password/privacy set to 'default' or other default values
  5. Confirm SNMP service accessibility
    Run 'show snmp' in the controller CLI to confirm SNMP is enabled, then verify network access controls to determine if SNMP ports (161/UDP) are reachable from untrusted networks
    Affected if SNMP is enabled and accessible from networks outside the trusted management network

You are affected if your Cisco Wireless LAN Controller runs software version 7.0.x through 7.0.98.0 AND has any default SNMP credentials (community strings 'public'/'private' or SNMPv3 user 'default') still configured and SNMP is accessible.

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

Immediately change all default SNMP community strings and SNMPv3 credentials to unique, strong values; disable default SNMP accounts if not needed; restrict SNMP access to management networks via ACLs.

Fix this in Unified Wireless Network Solution Software 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-2010-2976 — 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-2010-2976 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