# CVE-1999-0179: Denial of service in n/a

> A remote attacker can cause Windows NT to crash or lock up by executing a specific directory change command on a file share.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 1999
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-hh43-c3j2-vcx4

## What is CVE-1999-0179?

CVE-1999-0179 is a medium-severity denial of service vulnerability in Microsoft Windows Nt, published on 29 Sep 1999. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Windows NT crashes or locks up when a Samba client executes a "cd .." command on a file share.

Weakness: CWE-17

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

It affects 2 products.


Products: Microsoft Windows 95, Microsoft Windows Nt.

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

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

## Is CVE-1999-0179 being exploited?

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

## Other vulnerabilities in Microsoft Windows Nt

- [CVE-1999-0387](https://insights.sbomify.com/CVE-1999-0387/): Information disclosure in n/a (high 7.8)
- [CVE-2000-0330](https://insights.sbomify.com/CVE-2000-0330/): Memory corruption in n/a (high 7.6)
- [CVE-1999-0518](https://insights.sbomify.com/CVE-1999-0518/): Weak cryptography in n/a (high 7.5)
- [CVE-2000-0155](https://insights.sbomify.com/CVE-2000-0155/): Code injection in n/a (high 7.2)
- [CVE-2000-0979](https://insights.sbomify.com/CVE-2000-0979/): Auth bypass in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0179 is a medium-severity denial of service vulnerability in Microsoft Windows Nt, published on 29 Sep 1999. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-1999-0179 in the wild and no public exploit code.

Affected product: Microsoft Windows Nt. 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-0179/ (Markdown: https://insights.sbomify.com/CVE-1999-0179/index.md)
```

## Sources

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

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