dbcve.org
Unified Wireless Network Solution SoftwareOperating system · Cisco

CVE-2010-2982

HIGH · 7.1 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 →
80/100
Remediation priority · High
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
Cisco Unified Wireless Network (UWN) Solution 7.x before 7.0.98.0 allows remote attackers to discover a group password via a series of SNMP requests, as demonstrated by an SNMP walk, aka Bug ID CSCtb74037.

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

Cisco Unified Wireless Network Solution 7.x before 7.0.98.0 contains a vulnerability where remote attackers can discover the group password through a series of SNMP requests (SNMP walk). The vulnerability allows unauthenticated or low-privilege attackers to retrieve sensitive group password information via SNMP queries.

MitigationUpgrade to Cisco UWN Solution version 7.0.98.0 or later. Alternatively, restrict SNMP access via ACLs, change default community strings, and disable SNMP read-write access where possible.

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
M
Authentication
None
Confidentiality
Complete
Integrity
None
Availability
None

AV:N/AC:M/Au:N/C:C/I:N/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. Identify Cisco UWN Solution installation
    Locate any Cisco wireless controllers, access points, or management systems running the Cisco Unified Wireless Network Solution software in your environment. Check device inventory or network documentation for Cisco wireless products.
    Affected if The environment contains Cisco Unified Wireless Network Solution devices on version 7.0 through 7.0.98.0.
  2. Determine the installed software version
    Log into the Cisco wireless controller or access point CLI and run 'show version' or access the web interface to view the software version. Compare the version number against the affected range of 7.0 through versions before 7.0.98.0.
    Affected if The running version is 7.0.x or 7.0.98.0 specifically, indicating it is within or at the boundary of the affected range.
  3. Verify SNMP service status
    Check if SNMP is enabled on the Cisco wireless device by running 'show snmp' in the CLI or reviewing the SNMP configuration via the web interface. Confirm whether SNMP is active and listening on standard ports 161/162.
    Affected if SNMP is enabled and running on the device.
  4. Check SNMP community string configuration
    Run 'show snmp community' or review the SNMP community strings configured on the device. Identify whether default community strings (such as 'public' or 'private') are in use and whether read-write access is granted.
    Affected if Default or weak SNMP community strings are configured, or SNMP read-write access is enabled.
  5. Assess SNMP access exposure
    Determine if the SNMP service is accessible from untrusted networks or the internet by reviewing firewall rules, ACLs, and network segmentation. Attempt a test SNMP query from an untrusted segment if authorized to confirm accessibility.
    Affected if SNMP service is exposed to untrusted networks or unauthenticated attackers can reach UDP port 161.

The environment is affected if Cisco Unified Wireless Network Solution software versions 7.0 through 7.0.98.0 are running with SNMP enabled and accessible to unauthenticated or low-privilege attackers.

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

Upgrade to Cisco UWN Solution version 7.0.98.0 or later. Alternatively, restrict SNMP access via ACLs, change default community strings, and disable SNMP read-write access where possible.

Fix this in Unified Wireless Network Solution Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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