# CVE-2002-0526: Other in n/a

> Insecure file operations in INN news server utilities allow attackers to execute arbitrary code via crafted news articles.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-7rf7-f36g-27fc

## What is CVE-2002-0526?

CVE-2002-0526 is a high-severity vulnerability in n/a, published on 11 Jun 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in (1) inews or (2) rnews for INN 2.2.3 and earlier, related to insecure open() calls.

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

It affects 1 product.


Products: Inn Inn.

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

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

## Is CVE-2002-0526 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0526 is a high-severity vulnerability in n/a, published on 11 Jun 2002. 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-2002-0526 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-0526/ (Markdown: https://insights.sbomify.com/CVE-2002-0526/index.md)
```

## Sources

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

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