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

> Local attackers can read world-readable log files in EMC NetWorker to access sensitive information and potentially escalate privileges.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 15 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-69hg-682r-3m3v

## What is CVE-2002-0113?

CVE-2002-0113 is a medium-severity vulnerability in n/a, published on 15 Mar 2002. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

EMC NetWorker (formerly Legato NetWorker) before 7.0 stores log files in the /nsr/logs/ directory with world-readable permissions, which allows local users to read sensitive information and possibly gain privileges.  NOTE: this was originally reported for Legato NetWorker 6.1 on the Solaris 7 platform.

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

It affects 1 product.


Products: Emc Networker.

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

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

## Is CVE-2002-0113 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3892](https://insights.sbomify.com/CVE-2006-3892/): Auth bypass in n/a (critical 10.0)
- [CVE-2016-0916](https://insights.sbomify.com/CVE-2016-0916/): Auth bypass in n/a (critical 9.8)
- [CVE-2012-4607](https://insights.sbomify.com/CVE-2012-4607/): Memory corruption in n/a (critical 9.3)
- [CVE-2012-2288](https://insights.sbomify.com/CVE-2012-2288/): Memory corruption in n/a (critical 9.3)
- [CVE-2012-0395](https://insights.sbomify.com/CVE-2012-0395/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0113 is a medium-severity vulnerability in n/a, published on 15 Mar 2002. 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-0113 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-0113/ (Markdown: https://insights.sbomify.com/CVE-2002-0113/index.md)
```

## Sources

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

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