# CVE-2010-1574: Hardcoded credentials in n/a

> Remote attackers can modify configuration or read sensitive data on Cisco IE 3000 switches due to default SNMP community strings.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hqc8-q9j9-3wxj

## What is CVE-2010-1574?

CVE-2010-1574 is a critical vulnerability in Cisco Ios, published on 8 Jul 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-264

## Which versions are affected by CVE-2010-1574?

It affects 2 products.


Products: Cisco Industrial Ethernet 3000, Cisco Ios.

## How do I fix CVE-2010-1574?

No fix has been published for CVE-2010-1574 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-1574 being exploited?

There is no known exploitation of CVE-2010-1574 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1574 and fix it if it is affected.

What it is: CVE-2010-1574 is a critical vulnerability in Cisco Ios, published on 8 Jul 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-1574 in the wild and no public exploit code.

Affected product: Cisco Ios. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2010-1574/ (Markdown: https://insights.sbomify.com/CVE-2010-1574/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-1574
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-1574
- OSV: https://osv.dev/vulnerability/CVE-2010-1574

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-1574/
Summaries are generated and may contain mistakes; the official description above is the record.