# CVE-2005-1693: Integer overflow in n/a

> Remote attackers can execute arbitrary code and gain privileges via a crafted compressed VBA directory in the CA Vet Antivirus library.

- **Severity:** Critical 10.0 (`AV:N/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:** 24 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-23wf-qmmc-4cr6

## What is CVE-2005-1693?

CVE-2005-1693 is a critical vulnerability in n/a, published on 24 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer overflow in Computer Associates Vet Antivirus library, as used by CA InoculateIT 6.0, eTrust Antivirus r6.0 through 7.1, eTrust Antivirus for the Gateway r7.0 and r7.1, eTrust Secure Content Manager, eTrust Intrusion Detection, BrightStor ARCserve Backup (BAB) r11.1, Vet Antivirus, Zonelabs ZoneAlarm Security Suite, and ZoneAlarm Antivirus, allows remote attackers to gain privileges via a compressed VBA directory with a project name length of -1, which leads to a heap-based buffer overflow.

## Which versions are affected by CVE-2005-1693?

It affects 14 products.


Products: Broadcom Etrust Antivirus, Broadcom Etrust Antivirus Ee, Broadcom Etrust Ez Armor, Broadcom Etrust Ez Armor Le, Broadcom Etrust Intrusion Detection, Broadcom Etrust Secure Content Manager, Broadcom Inoculateit, Ca Brightstor Arcserve Backup, Ca Etrust Antivirus, Ca Etrust Intrusion Detection, Ca Etrust Secure Content Manager, Ca Vet Antivirus, Zonelabs Zonealarm, Zonelabs Zonealarm Antivirus.

## How do I fix CVE-2005-1693?

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

## Is CVE-2005-1693 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3223](https://insights.sbomify.com/CVE-2006-3223/): Other in n/a (high 7.5)
- [CVE-2006-6496](https://insights.sbomify.com/CVE-2006-6496/): Null dereference in n/a (medium 6.6)
- [CVE-2005-3372](https://insights.sbomify.com/CVE-2005-3372/): Security feature bypass in n/a (medium 5.1)
- [CVE-2005-3225](https://insights.sbomify.com/CVE-2005-3225/): Security feature bypass in n/a (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1693 and fix it if it is affected.

What it is: CVE-2005-1693 is a critical vulnerability in n/a, published on 24 May 2005. 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-2005-1693 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-2005-1693/ (Markdown: https://insights.sbomify.com/CVE-2005-1693/index.md)
```

## Sources

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

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