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

> Remote attackers can exploit improper file name filtering in the DCC server command to place malicious files and potentially execute commands.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Feb 2000
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-mcv3-c4v3-2pf4

## What is CVE-1999-0399?

CVE-1999-0399 is a high-severity path traversal vulnerability in n/a, published on 4 Feb 2000. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The DCC server command in the Mirc 5.5 client doesn't filter characters from file names properly, allowing remote attackers to place a malicious file in a different location, possibly allowing the attacker to execute commands.

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

It affects 1 product.


Products: Khaled Mardam-Bey Mirc.

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

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

## Is CVE-1999-0399 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1456](https://insights.sbomify.com/CVE-2002-1456/): Memory corruption in n/a (high 7.5)
- [CVE-2002-0231](https://insights.sbomify.com/CVE-2002-0231/): Memory corruption in n/a (high 7.5)
- [CVE-2001-0315](https://insights.sbomify.com/CVE-2001-0315/): Security feature bypass in n/a (high 7.5)
- [CVE-2001-0944](https://insights.sbomify.com/CVE-2001-0944/): Privilege escalation in n/a (high 7.2)
- [CVE-2003-1512](https://insights.sbomify.com/CVE-2003-1512/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0399 is a high-severity path traversal vulnerability in n/a, published on 4 Feb 2000. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-1999-0399 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-0399/ (Markdown: https://insights.sbomify.com/CVE-1999-0399/index.md)
```

## Sources

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

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