dbcve.org
Network Analysis ModuleHardware / appliance · Cisco

CVE-2007-1257

HIGH · 10.0 CVSS v2.0 Published 2007-03-03
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 Network Analysis Module (NAM) in Cisco Catalyst Series 6000, 6500, and 7600 allows remote attackers to execute arbitrary commands via certain SNMP packets that are spoofed from the NAM's own IP address.

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 · moderate confidence

The Network Analysis Module (NAM) in Cisco Catalyst 6000, 6500, and 7600 series switches contains a vulnerability allowing remote command execution via specially crafted SNMP packets spoofed to appear to originate from the NAM's own IP address, bypassing typical source validation.

MitigationRestrict SNMP access to trusted management networks, implement SNMPv3 with authentication and encryption, and consider disabling unnecessary SNMP access on affected devices.

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
Network Analysis ModuleHardware / appliance
Affected:all versions
Catalyst 6000 Ws Svc Nam 1Hardware / appliance
Affected:= 2.2\(1a\)
Catalyst 6000 Ws Svc Nam 2Hardware / appliance
Affected:= 2.2\(1a\)
Catalyst 6000 Ws X6380 NamHardware / appliance
Affected:= 3.1\(1a\)
Catalyst 6500 Ws Svc Nam 1Hardware / appliance
Affected:= 2.2\(1a\)
Catalyst 6500 Ws Svc Nam 2Hardware / appliance
Affected:= 2.2\(1a\)
Catalyst 6500 Ws X6380 NamHardware / appliance
Affected:= 3.1\(1a\)
Catalyst 7600 Ws Svc Nam 1Hardware / appliance
Affected:= 2.2\(1a\)

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 if a Cisco NAM module is installed
    Check the device hardware inventory or running configuration for NAM (Network Analysis Module) presence on Catalyst 6000, 6500, or 7600 series switches
    Affected if A Cisco Network Analysis Module is present in the device inventory
  2. Determine the exact NAM software version
    Use the command to display NAM module version information (typically via 'show module' or 'show hardware' command for the NAM line card)
    Affected if The installed version matches 2.2(1a) or 3.1(1a), or falls within the 'all versions' category for the general Cisco NAM product
  3. Verify if SNMP is enabled on the device
    Check the device configuration for any SNMP-related commands (such as 'snmp-server' configuration lines)
    Affected if SNMP is enabled and configured on the device or the NAM module
  4. Check SNMP community strings and access control
    Review SNMP configuration for community string settings and access lists that control which IP addresses can use SNMP
    Affected if SNMP is accessible from untrusted networks or uses default community strings without proper access restrictions
  5. Confirm NAM management IP address configuration
    Examine the NAM module IP address configuration to understand its management interface and network exposure
    Affected if The NAM management interface is reachable from networks beyond the trusted management segment

A user is affected if they have a Cisco NAM module (any version, or specifically 2.2(1a)/3.1(1a) versions listed) running on Catalyst 6000/6500/7600 series hardware with SNMP access enabled and exposed to potentially untrusted networks.

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

Restrict SNMP access to trusted management networks, implement SNMPv3 with authentication and encryption, and consider disabling unnecessary SNMP access on affected devices.

Fix this in Network Analysis Module Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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 locally
dbcve dependency scanner

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