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

> Local attackers can execute arbitrary code or crash the system via a crafted IOCTL request in the Panda Internet Security kernel driver.

- **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:** 24 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-38mc-jpfh-xh7r

## What is CVE-2008-1471?

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

### Official description

The cpoint.sys driver in Panda Internet Security 2008 and Antivirus+ Firewall 2008 allows local users to cause a denial of service (system crash or kernel panic), overwrite memory, or execute arbitrary code via a crafted IOCTL request that triggers an out-of-bounds write of kernel memory.

Weakness: CWE-399

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

It affects 2 products.


Products: Panda Panda Antivirus and Firewall, Panda Panda Internet Security.

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

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

## Is CVE-2008-1471 being exploited?

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

Public exploit code:

- Panda Internet Security/AntiVirus+Firewall 2008 - 'CPoint.sys' Memory Corruption (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-1471 is a high-severity memory corruption vulnerability in n/a, published on 24 Mar 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-1471 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-1471/ (Markdown: https://insights.sbomify.com/CVE-2008-1471/index.md)
```

## Sources

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

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