# CVE-1999-1368: Security feature bypass in n/a

> Antivirus plugin fails to scan moved emails, allowing viruses to bypass detection if user rules relocate messages.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Sep 2001
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-qgqh-3fh5-37xc

## What is CVE-1999-1368?

CVE-1999-1368 is a high-severity vulnerability in n/a, published on 12 Sep 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AV Option for MS Exchange Server option for InoculateIT 4.53, and possibly other versions, only scans the Inbox folder tree of a Microsoft Exchange server, which could allow viruses to escape detection if a user's rules cause the message to be moved to a different mailbox.

## Which versions are affected by CVE-1999-1368?

It affects 1 product.


Products: Broadcom Inoculateit.

## How do I fix CVE-1999-1368?

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

## Is CVE-1999-1368 being exploited?

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

## Other vulnerabilities in n/a

- [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-2002-2285](https://insights.sbomify.com/CVE-2002-2285/): Security feature bypass in n/a (medium 4.3)
- [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-1999-1368 and fix it if it is affected.

What it is: CVE-1999-1368 is a high-severity vulnerability in n/a, published on 12 Sep 2001. 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-1999-1368 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-1999-1368/ (Markdown: https://insights.sbomify.com/CVE-1999-1368/index.md)
```

## Sources

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

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