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

> Malicious websites can determine the existence of files on Windows 2000 systems with Indexing Services enabled via a safe ActiveX object.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Dec 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-hrjf-28rx-wf7r

## What is CVE-2000-1105?

CVE-2000-1105 is a medium-severity vulnerability in n/a, published on 19 Dec 2000. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The ixsso.query ActiveX Object is marked as safe for scripting, which allows malicious web site operators to embed a script that remotely determines the existence of files on visiting Windows 2000 systems that have Indexing Services enabled.

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

It affects 1 product.


Products: Microsoft Indexing Service.

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

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

## Is CVE-2000-1105 being exploited?

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

Public exploit code:

- Microsoft Indexing Service (Windows 2000) - File Verification (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0942](https://insights.sbomify.com/CVE-2000-0942/): Cross-site scripting in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-1105 is a medium-severity vulnerability in n/a, published on 19 Dec 2000. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-1105 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-1105/ (Markdown: https://insights.sbomify.com/CVE-2000-1105/index.md)
```

## Sources

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

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