# CVE-2002-2285: Security feature bypass in n/a

> Remote attackers can bypass virus detection in eTrust InoculateIT by exploiting a race condition during incremental scans of partially downloaded files.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-8g23-v7v7-6hqq

## What is CVE-2002-2285?

CVE-2002-2285 is a medium-severity vulnerability in n/a, published on 18 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

eTrust InoculateIT 6.0 with the "Incremental Scan" option enabled may certify that a file is free of viruses before the file has been completely downloaded, which allows remote attackers to bypass virus detection.

Weakness: CWE-16

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

It affects 1 product.


Products: Broadcom Inoculateit.

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

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

## Is CVE-2002-2285 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-1999-1368](https://insights.sbomify.com/CVE-1999-1368/): Security feature bypass in n/a (high 7.5)
- [CVE-2001-0625](https://insights.sbomify.com/CVE-2001-0625/): Path traversal in n/a (high 7.2)
- [CVE-2004-2092](https://insights.sbomify.com/CVE-2004-2092/): Misconfiguration in n/a (medium 4.6)
- [CVE-2004-0267](https://insights.sbomify.com/CVE-2004-0267/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2285 is a medium-severity vulnerability in n/a, published on 18 Oct 2007. 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-2285 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-2285/ (Markdown: https://insights.sbomify.com/CVE-2002-2285/index.md)
```

## Sources

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

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