# CVE-2004-2092: Misconfiguration in n/a

> Local attackers can delete, modify, or view sensitive information due to insecure file permissions in eTrust InoculateIT for Linux.

- **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:** 19 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-86vf-f629-7p49

## What is CVE-2004-2092?

CVE-2004-2092 is a medium-severity vulnerability in n/a, published on 19 May 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

eTrust InoculateIT for Linux 6.0 uses insecure permissions for multiple files and directories, including the application's registry and tmp directories, which allows local users to delete, modify, or examine sensitive information.

## Which versions are affected by CVE-2004-2092?

It affects 1 product.


Products: Broadcom Inoculateit.

## How do I fix CVE-2004-2092?

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

## Is CVE-2004-2092 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-1999-1368](https://insights.sbomify.com/CVE-1999-1368/): Security feature bypass in n/a (high 7.5)
- [CVE-2001-0625](https://insights.sbomify.com/CVE-2001-0625/): Path traversal in n/a (high 7.2)
- [CVE-2002-2285](https://insights.sbomify.com/CVE-2002-2285/): Security feature bypass in n/a (medium 4.3)
- [CVE-2004-0267](https://insights.sbomify.com/CVE-2004-0267/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2092 and fix it if it is affected.

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

## Sources

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

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