# CVE-1999-1126: Information disclosure in n/a

> Local attackers can read sensitive configuration data like passwords and SNMP strings from insecurely permissioned log files in Cisco Resource Manager.

- **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:** 12 Sep 2001
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-fvh2-cqvp-vwxx

## What is CVE-1999-1126?

CVE-1999-1126 is a low-severity vulnerability in n/a, published on 12 Sep 2001. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cisco Resource Manager (CRM) 1.1 and earlier creates certain files with insecure permissions that allow local users to obtain sensitive configuration information including usernames, passwords, and SNMP community strings, from (1) swim_swd.log, (2) swim_debug.log, (3) dbi_debug.log, and (4) temporary files whose names begin with "DPR_".

## Which versions are affected by CVE-1999-1126?

It affects 1 product.


Products: Cisco Resource Manager.

## How do I fix CVE-1999-1126?

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

## Is CVE-1999-1126 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-1999-1042](https://insights.sbomify.com/CVE-1999-1042/): Information disclosure in n/a (low 1.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-1126 and fix it if it is affected.

What it is: CVE-1999-1126 is a low-severity vulnerability in n/a, published on 12 Sep 2001. 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-1999-1126 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-1999-1126/ (Markdown: https://insights.sbomify.com/CVE-1999-1126/index.md)
```

## Sources

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

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