# CVE-2007-2151: Denial of service in n/a

> Remote attackers can crash the McAfee e-Business Server administration service by sending a malformed authentication packet with a large length value.

- **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:** 19 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7mcr-4h6g-w464

## What is CVE-2007-2151?

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

### Official description

The administration server in McAfee e-Business Server before 8.1.1 and 8.5.x before 8.5.2 allows remote attackers to cause a denial of service (service crash) via a large length value in a malformed authentication packet, which triggers a heap over-read.

## Which versions are affected by CVE-2007-2151?

It affects 1 product.


Products: Mcafee E-Business Server.

## How do I fix CVE-2007-2151?

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

## Is CVE-2007-2151 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2957](https://insights.sbomify.com/CVE-2007-2957/): Integer overflow in n/a (critical 9.3)
- [CVE-2008-0127](https://insights.sbomify.com/CVE-2008-0127/): Memory corruption in n/a (high 8.8)
- [CVE-2006-5271](https://insights.sbomify.com/CVE-2006-5271/): Integer overflow in n/a (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2151 and fix it if it is affected.

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

## Sources

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

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