dbcve.org
iOSOperating system · Cisco

CVE-2010-1574

HIGH · 10.0 CVSS v2.0 Published 2010-07-08
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
IOS 12.2(52)SE and 12.2(52)SE1 on Cisco Industrial Ethernet (IE) 3000 series switches has (1) a community name of public for RO access and (2) a community name of private for RW access, which makes it easier for remote attackers to modify the configuration or obtain potentially sensitive information via SNMP requests, aka Bug ID CSCtf25589.

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 IE 3000 switches running IOS 12.2(52)SE and 12.2(52)SE1 ship with hardcoded default SNMP community strings 'public' (read-only) and 'private' (read-write). Attackers can exploit these known default credentials via SNMP to read sensitive device configuration, topology, and performance data, or to modify device settings.

MitigationChange the default SNMP community strings to unique, complex values and apply ACLs to restrict SNMP access to trusted management networks, or disable SNMP if not operationally required.

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
iOSOperating system
Affected:= 12.2\(52\)se= 12.2\(52\)se1
Industrial Ethernet 3000Hardware / appliance
Affected:all versions

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. Check the IOS version
    Run 'show version' on the device CLI and look for version string 12.2(52)SE or 12.2(52)SE1
    Affected if Version is 12.2(52)SE or 12.2(52)SE1, or device is a Cisco Industrial Ethernet 3000 with any IOS version
  2. Confirm device model
    Run 'show version' or 'show inventory' to identify if the device is a Cisco Industrial Ethernet 3000 switch
    Affected if Device is a Cisco IE 3000 switch
  3. Check if SNMP is enabled
    Run 'show snmp' or 'show running-config | include snmp' to see if SNMP is configured
    Affected if SNMP is enabled and community strings are configured
  4. Inspect SNMP community string configuration
    Run 'show snmp group' or 'show running-config | include snmp community' to view configured community strings
    Affected if The default community strings 'public' (read-only) or 'private' (read-write) are present in the configuration

A user is affected if they have a Cisco IE 3000 switch or IOS 12.2(52)SE/SE1 with SNMP enabled and the default community strings 'public' or 'private' 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Change the default SNMP community strings to unique, complex values and apply ACLs to restrict SNMP access to trusted management networks, or disable SNMP if not operationally required.

Fix this in iOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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