# CVE-2002-1970: Information disclosure in n/a

> Local attackers can read world-writable temporary files to steal alert database credentials when SnortCenter pushes rules.

- **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:** 28 Jun 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-77fh-vp9q-jhpc

## What is CVE-2002-1970?

CVE-2002-1970 is a low-severity vulnerability in n/a, published on 28 Jun 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SnortCenter 0.9.5, when configured to push Snort rules, stores the rules in a temporary file with world-readable and world-writable permissions, which allows local users to obtain usernames and passwords for the alert database servers.

## Which versions are affected by CVE-2002-1970?

It affects 1 product.


Products: Snortcenter Snortcenter.

## How do I fix CVE-2002-1970?

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

## Is CVE-2002-1970 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1970 and fix it if it is affected.

What it is: CVE-2002-1970 is a low-severity vulnerability in n/a, published on 28 Jun 2005. 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-2002-1970 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-2002-1970/ (Markdown: https://insights.sbomify.com/CVE-2002-1970/index.md)
```

## Sources

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

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