# CVE-1999-1289: Information disclosure in n/a

> Remote attackers can obtain the internal IP address of ICQ clients by analyzing TCP packet data, revealing sensitive network configuration details.

- **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:** 12 Sep 2001
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-34v6-99gm-vhvc

## What is CVE-1999-1289?

CVE-1999-1289 is a high-severity vulnerability in n/a, published on 12 Sep 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ICQ 98 beta on Windows NT leaks the internal IP address of a client in the TCP data segment of an ICQ packet instead of the public address (e.g. through NAT), which provides remote attackers with potentially sensitive information about the client or the internal network configuration.

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

It affects 1 product.


Products: Mirabilis Icq.

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

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

## Is CVE-1999-1289 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2329](https://insights.sbomify.com/CVE-2002-2329/): Denial of service in n/a (high 7.8)
- [CVE-2006-4662](https://insights.sbomify.com/CVE-2006-4662/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0235](https://insights.sbomify.com/CVE-2003-0235/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0236](https://insights.sbomify.com/CVE-2003-0236/): Integer overflow in n/a (high 7.5)
- [CVE-2003-0237](https://insights.sbomify.com/CVE-2003-0237/): Supply chain in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-1289 is a high-severity vulnerability in n/a, published on 12 Sep 2001. 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-1289 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-1289/ (Markdown: https://insights.sbomify.com/CVE-1999-1289/index.md)
```

## Sources

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

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