# CVE-2002-0131: Information disclosure in n/a

> Remote attackers can read arbitrary client files via malicious web pages using the ActivePython ActiveX control in Internet Explorer.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-v8w7-8vj5-pjjm

## What is CVE-2002-0131?

CVE-2002-0131 is a medium-severity vulnerability in n/a, published on 15 Mar 2002. 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

ActivePython ActiveX control for Python in the AXScript package, when used in Internet Explorer, does not prevent a script from reading files from the client's filesystem, which allows remote attackers to read arbitrary files via a malicious web page containing Python script.

## Which versions are affected by CVE-2002-0131?

It affects 1 product.


Products: Activestate Activepython.

## How do I fix CVE-2002-0131?

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

## Is CVE-2002-0131 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-5379](https://insights.sbomify.com/CVE-2012-5379/): Privilege escalation in n/a (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0131 and fix it if it is affected.

What it is: CVE-2002-0131 is a medium-severity vulnerability in n/a, published on 15 Mar 2002. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-0131 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-2002-0131/ (Markdown: https://insights.sbomify.com/CVE-2002-0131/index.md)
```

## Sources

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

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