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

> Remote attackers can crash Apani Networks EpiForce IPSec software by sending malicious IKEv1 packets, causing a denial of service.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 17 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h78m-q2g5-r2v4

## What is CVE-2005-4321?

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

### Official description

The Internet Key Exchange version 1 (IKEv1) implementation in Apani Networks EpiForce 1.9 and earlier running IPSec, allow remote attackers to cause a denial of service (crash) via certain IKE packets, as demonstrated by the PROTOS ISAKMP Test Suite for IKEv1. NOTE: due to the lack of details in the advisory, it is unclear which of CVE-2005-3666, CVE-2005-3667, and/or CVE-2005-3668 this issue applies to.

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

It affects 1 product.


Products: Apani Networks Epiforce Agent.

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

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

## Is CVE-2005-4321 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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