# CVE-1999-0007: Weak cryptography in n/a

> Attackers can obtain information from SSL-encrypted sessions via PKCS #1, compromising data confidentiality.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 29 Sep 1999
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-52pp-8p9h-45f8

## What is CVE-1999-0007?

CVE-1999-0007 is a medium-severity vulnerability in Microsoft Exchange Server, published on 29 Sep 1999. 

### Official description

Information from SSL-encrypted sessions via PKCS #1.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 13 products.


Products: C2net Stonghold Web Server, Hp Open Market Secure Webserver, Microsoft Exchange Server, Microsoft Internet Information Server, Microsoft Site Server, Netscape Certificate Server, Netscape Collabra Server, Netscape Directory Server, Netscape Enterprise Server, Netscape Fasttrack Server, Netscape Messaging Server, Netscape Proxy Server, Ssleay Ssleay.

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

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

## Is CVE-1999-0007 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0007 is a medium-severity vulnerability in Microsoft Exchange Server, published on 29 Sep 1999. 
Exploitation: There is no known exploitation of CVE-1999-0007 in the wild and no public exploit code.

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

## Sources

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

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