# CVE-1999-0753: Path traversal in n/a

> Remote attackers can view restricted directories via the w3-msql CGI script in Mini SQL, exposing sensitive file information.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2000
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-3pqj-chvj-wmcp

## What is CVE-1999-0753?

CVE-1999-0753 is a high-severity path traversal vulnerability in n/a, published on 18 Jan 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The w3-msql CGI script provided with Mini SQL allows remote attackers to view restricted directories.

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

It affects 1 product.


Products: Hughes Msql.

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

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

## Is CVE-1999-0753 being exploited?

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

Public exploit code:

- Hughes Technologies Mini SQL (mSQL) 2.0/2.0.10 - Information Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0012](https://insights.sbomify.com/CVE-2000-0012/): Memory corruption in n/a (critical 10.0)
- [CVE-1999-1260](https://insights.sbomify.com/CVE-1999-1260/): Information disclosure in n/a (high 7.5)
- [CVE-1999-0276](https://insights.sbomify.com/CVE-1999-0276/): Memory corruption in n/a (high 7.5)
- [CVE-2001-1225](https://insights.sbomify.com/CVE-2001-1225/): Denial of service in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0753 is a high-severity path traversal vulnerability in n/a, published on 18 Jan 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-1999-0753 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-1999-0753/ (Markdown: https://insights.sbomify.com/CVE-1999-0753/index.md)
```

## Sources

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

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