# CVE-2000-0552: Information disclosure in n/a

> Local attackers can read sensitive information from world-readable temporary files created during login in the ICQ webmail client.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-55c6-r3wh-x7cj

## What is CVE-2000-0552?

CVE-2000-0552 is a medium-severity vulnerability in n/a, published on 13 Oct 2000. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ICQwebmail client for ICQ 2000A creates a world readable temporary file during login and does not delete it, which allows local users to obtain sensitive information.

Weakness: CWE-459 (Incomplete Cleanup)

## Which versions are affected by CVE-2000-0552?

It affects 1 product.


Products: Icq Icq.

## How do I fix CVE-2000-0552?

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

## Is CVE-2000-0552 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0552 exists.

Public exploit code:

- Mirabilis ICQ 2000.0 A - Mailclient Temporary Link (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2011-0487](https://insights.sbomify.com/CVE-2011-0487/): Code injection in n/a (critical 9.3)
- [CVE-2009-1915](https://insights.sbomify.com/CVE-2009-1915/): Stack-based buffer overflow in the URL Search Hook (ICQToolBar.dll) in ICQ 6.5 allows remote attackers to cause a denial of service (persist (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0552 and fix it if it is affected.

What it is: CVE-2000-0552 is a medium-severity vulnerability in n/a, published on 13 Oct 2000. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0552 exists.

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-2000-0552/ (Markdown: https://insights.sbomify.com/CVE-2000-0552/index.md)
```

## Sources

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

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