# CVE-2006-1210: Hardcoded credentials in n/a

> Remote attackers can read cleartext MySQL credentials from a web interface file to gain database privileges in IBM Tivoli Micromuse Netcool/NeuSecure.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qx23-p4v5-5xrm

## What is CVE-2006-1210?

CVE-2006-1210 is a high-severity vulnerability in n/a, published on 14 Mar 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web interface for IBM Tivoli Micromuse Netcool/NeuSecure 3.0.236 includes the MySQL database username and password in cleartext in body.phtml, which allows remote attackers to gain privileges by reading the source.  NOTE: IBM has privately confirmed to CVE that a fix is available for these issues.

## Which versions are affected by CVE-2006-1210?

It affects 1 product.


Products: Micromuse Netcool Neusecure.

## How do I fix CVE-2006-1210?

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

## Is CVE-2006-1210 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-1211](https://insights.sbomify.com/CVE-2006-1211/): Misconfiguration in n/a (high 7.5)
- [CVE-2006-0837](https://insights.sbomify.com/CVE-2006-0837/): Information disclosure in n/a (low 2.1)
- [CVE-2006-0838](https://insights.sbomify.com/CVE-2006-0838/): Hardcoded credentials in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1210 and fix it if it is affected.

What it is: CVE-2006-1210 is a high-severity vulnerability in n/a, published on 14 Mar 2006. 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-2006-1210 in the wild and no public exploit code.

Affected product: n/a. 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-2006-1210/ (Markdown: https://insights.sbomify.com/CVE-2006-1210/index.md)
```

## Sources

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

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