# CVE-2005-0968: Denial of service in n/a

> Remote attackers can cause a denial of service in CA eTrust Intrusion Detection by sending large size values to the Crypto API.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 5 Apr 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-q72g-cr9m-mjq9

## What is CVE-2005-0968?

CVE-2005-0968 is a medium-severity denial of service vulnerability in n/a, published on 5 Apr 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Computer Associates (CA) eTrust Intrusion Detection 3.0 allows remote attackers to cause a denial of service via large size values that are not properly validated before calling the CPImportKey function in the Crypto API.

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

It affects 1 product.


Products: Broadcom Etrust Intrusion Detection.

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

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

## Is CVE-2005-0968 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3302](https://insights.sbomify.com/CVE-2007-3302/): Code injection in n/a (critical 9.3)
- [CVE-2007-1005](https://insights.sbomify.com/CVE-2007-1005/): Memory corruption in n/a (high 7.8)
- [CVE-2000-0559](https://insights.sbomify.com/CVE-2000-0559/): Weak cryptography in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0968 is a medium-severity denial of service vulnerability in n/a, published on 5 Apr 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-0968 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-0968/ (Markdown: https://insights.sbomify.com/CVE-2005-0968/index.md)
```

## Sources

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

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