# CVE-2008-5048: Memory corruption in n/a

> Local attackers can trigger a buffer overflow in the Anti-Trojan Elite driver via IOCTL, potentially causing a crash or executing arbitrary code.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pxv7-mjvv-77vw

## What is CVE-2008-5048?

CVE-2008-5048 is a high-severity memory corruption vulnerability in n/a, published on 13 Nov 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer overflow in Atepmon.sys in ISecSoft Anti-Trojan Elite 4.2.1 and earlier, and possibly 4.2.2, allows local users to cause a denial of service (crash) and possibly execute arbitrary code via long inputs to the 0x00222494 IOCTL.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-5048?

It affects 1 product.


Products: Isecsoft Anti-Trojan Elite.

## How do I fix CVE-2008-5048?

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

## Is CVE-2008-5048 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5048 exists.

Public exploit code:

- Anti-Trojan Elite 4.2.1 - 'Atepmon.sys' IOCTL Request Local Overflow / Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5048 and fix it if it is affected.

What it is: CVE-2008-5048 is a high-severity memory corruption vulnerability in n/a, published on 13 Nov 2008. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5048 exists.

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-2008-5048/ (Markdown: https://insights.sbomify.com/CVE-2008-5048/index.md)
```

## Sources

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

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