# CVE-2007-0005: Memory corruption in n/a

> Local attackers can exploit buffer overflows in the Omnikey CardMan 4040 driver to gain elevated privileges on Linux systems.

- **Severity:** Medium 6.9 (`AV:L/AC:M/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:** Yes
- **Published:** 10 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wqq7-6mh4-2rxq

## What is CVE-2007-0005?

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

### Official description

Multiple buffer overflows in the (1) read and (2) write handlers in the Omnikey CardMan 4040 driver in the Linux kernel before 2.6.21-rc3 allow local users to gain privileges.

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

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

It affects 1 product.


Products: Omnikey.aaitg Omnikey Cardman 4040.

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

Upgrade to a fixed version.

## Is CVE-2007-0005 being exploited?

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

Public exploit code:

- Linux Omnikey Cardman 4040 Driver - Local Buffer Overflow (PoC) (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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