# CVE-1999-1403: Misconfiguration in n/a

> Local attackers can exploit insecure file permissions in IBM Tivoli OPC Tracker Agent to disrupt operations or escalate privileges.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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-5h86-f8rg-c9qv

## What is CVE-1999-1403?

CVE-1999-1403 is a high-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

IBM/Tivoli OPC Tracker Agent version 2 release 1 creates files, directories, and IPC message queues with insecure permissions (world-readable and world-writable), which could allow local users to disrupt operations and possibly gain privileges by modifying or deleting files.

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

It affects 1 product.


Products: Ibm Tivoli Opc Tracker Agent.

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

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

## Is CVE-1999-1403 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-1999-1404](https://insights.sbomify.com/CVE-1999-1404/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-1403 is a high-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-1403 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-1403/ (Markdown: https://insights.sbomify.com/CVE-1999-1403/index.md)
```

## Sources

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

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