# CVE-1999-0519: Hardcoded credentials in n/a

> Attackers can access network shares without authentication due to default, null, or missing passwords, leading to unauthorized data access.

- **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:** 4 Feb 2000
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-vqfj-wqqj-3g3w

## What is CVE-1999-0519?

CVE-1999-0519 is a high-severity vulnerability in Microsoft Outlook, published on 4 Feb 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A NETBIOS/SMB share password is the default, null, or missing.

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

It affects 4 products.


Products: Microsoft Outlook, Microsoft Windows 2000, Microsoft Windows 95, Microsoft Windows Nt.

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

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

## Is CVE-1999-0519 being exploited?

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

## Other vulnerabilities in Microsoft Outlook

- [CVE-2017-11774](https://insights.sbomify.com/CVE-2017-11774/): Microsoft Office Outlook Security Feature Bypass (high 7.8, exploited in the wild)
- [CVE-2001-0538](https://insights.sbomify.com/CVE-2001-0538/): Code injection in n/a (critical 10.0)
- [CVE-2013-3870](https://insights.sbomify.com/CVE-2013-3870/): Use after free in n/a (critical 9.3)
- [CVE-2010-2728](https://insights.sbomify.com/CVE-2010-2728/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-0266](https://insights.sbomify.com/CVE-2010-0266/): Code injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0519 is a high-severity vulnerability in Microsoft Outlook, published on 4 Feb 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-1999-0519 in the wild and no public exploit code.

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

## Sources

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

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