CVE-2008-7095
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 · uneditedThe SNMP daemon in ArubaOS 3.3.2.6 in Aruba Mobility Controller does not restrict SNMP access, which allows remote attackers to (1) read all SNMP community strings via SNMP-COMMUNITY-MIB::snmpCommunityName (1.3.6.1.6.3.18.1.1.1.2) or SNMP-VIEW-BASED-ACM-MIB::vacmGroupName (1.3.6.1.6.3.16.1.2.1.3) with knowledge of one community string, and (2) read SNMPv3 user names via SNMP-USER-BASED-SM-MIB or SNMP-VIEW-BASED-ACM-MIB.
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 confidenceThe SNMP daemon in ArubaOS 3.3.2.6 on Aruba Mobility Controller does not enforce proper SNMP access controls. An attacker with knowledge of a single SNMP community string can read all configured community strings via specific OIDs (SNMP-COMMUNITY-MIB::snmpCommunityName and SNMP-VIEW-BASED-ACM-MIB::vacmGroupName), and can also enumerate SNMPv3 user names through SNMP-USER-BASED-SM-MIB or SNMP-VIEW-BASED-ACM-MIB.
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 dataall versions= 3.3.2.6CVSS 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
- None
- Availability
- None
AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device model and OSLog into the Aruba Mobility Controller CLI and run 'show version' to confirm the device is an Aruba Mobility Controller and note the ArubaOS versionAffected if The device is an Aruba Mobility Controller running ArubaOS version 3.3.2.6
-
Verify SNMP is enabledRun 'show snmp-server' or check the SNMP configuration via 'show running-config | include snmp' to see if SNMP is configuredAffected if SNMP is enabled on the device
-
Check SNMP community string configurationRun 'show snmp community' to list configured SNMP community stringsAffected if One or more SNMP community strings are configured and SNMP is enabled
-
Test access to vulnerable MIBsUsing an SNMP client (snmpwalk or snmpget), query the OIDs SNMP-COMMUNITY-MIB::snmpCommunityName (1.3.6.1.6.3.18.1.1) and SNMP-VIEW-BASED-ACM-MIB::vacmGroupName (1.3.6.1.6.3.16.1.5) using a known community stringAffected if The MIBs return sensitive data such as all configured community strings or SNMPv3 user groups without proper access restrictions
-
Check SNMPv3 user enumerationUsing an SNMP client, query SNMP-USER-BASED-SM-MIB::usmUserEntry (1.3.6.1.6.3.15.1.1) using a known community stringAffected if SNMPv3 usernames or user security names are exposed through the MIB
The device is affected if it is an Aruba Mobility Controller running ArubaOS 3.3.2.6 with SNMP enabled and the SNMP MIBs return sensitive community strings or user information without proper access control enforcement.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched ArubaOS version that properly restricts SNMP MIB access, or configure SNMP access control lists (ACLs) to limit which OIDs can be queried and by which management stations.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-7095 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2008-7095 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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