# CVE-2002-1514: Path traversal in n/a

> Local attackers can overwrite files via symlink attacks on temporary files to gain elevated privileges in Borland InterBase.

- **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:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-h56q-pf37-f5g7

## What is CVE-2002-1514?

CVE-2002-1514 is a high-severity path traversal vulnerability in n/a, published on 1 Sep 2004. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

gds_lock_mgr in Borland InterBase allows local users to overwrite files and gain privileges via a symlink attack on a "isc_init1.X" temporary file, as demonstrated by modifying the xinetdbd file.

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

It affects 1 product.


Products: Borland Software Interbase.

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

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

## Is CVE-2002-1514 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1514 exists.

Public exploit code:

- Interbase 5/6 - GDS_Lock_MGR UMask File Permission Changing (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-0008](https://insights.sbomify.com/CVE-2001-0008/): Auth bypass in n/a (critical 10.0)
- [CVE-2007-5243](https://insights.sbomify.com/CVE-2007-5243/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-5244](https://insights.sbomify.com/CVE-2007-5244/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-3566](https://insights.sbomify.com/CVE-2007-3566/): Memory corruption in n/a (high 7.5)
- [CVE-2004-1833](https://insights.sbomify.com/CVE-2004-1833/): Misconfiguration in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1514 is a high-severity path traversal vulnerability in n/a, published on 1 Sep 2004. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1514 exists.

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-1514/ (Markdown: https://insights.sbomify.com/CVE-2002-1514/index.md)
```

## Sources

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

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