# CVE-2006-0837: Information disclosure in n/a

> Local attackers can read sensitive configuration files containing passwords due to world-readable permissions in IBM Netcool NeuSecure.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pgxf-mp37-9rpp

## What is CVE-2006-0837?

CVE-2006-0837 is a low-severity vulnerability in n/a, published on 22 Feb 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Tivoli Micromuse Netcool/NeuSecure 3.0.236 has world-readable permissions for (1) /etc/neusecure.conf, (2) /opt/NeuSecure/etc/cms-3.0.236.buildconf, and (3) /opt/NeuSecure/bin/ns_archiver.log, which allows local users to read sensitive information such as passwords.  NOTE: IBM has privately confirmed to CVE that a fix is available for these issues.

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

It affects 1 product.


Products: Micromuse Netcool Neusecure.

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

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

## Is CVE-2006-0837 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-1210](https://insights.sbomify.com/CVE-2006-1210/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2006-1211](https://insights.sbomify.com/CVE-2006-1211/): Misconfiguration in n/a (high 7.5)
- [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-0837 and fix it if it is affected.

What it is: CVE-2006-0837 is a low-severity vulnerability in n/a, published on 22 Feb 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0837 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-0837/ (Markdown: https://insights.sbomify.com/CVE-2006-0837/index.md)
```

## Sources

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

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