# CVE-2006-6013: Integer overflow in n/a

> Local attackers can read arbitrary memory contents via an integer signedness error in BSD kernel FireWire drivers.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **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:** 21 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6jjw-8xq9-mjfm

## What is CVE-2006-6013?

CVE-2006-6013 is a low-severity vulnerability in Freebsd Freebsd, published on 21 Nov 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integer signedness error in the fw_ioctl (FW_IOCTL) function in the FireWire (IEEE-1394) drivers (dev/firewire/fwdev.c) in various BSD kernels, including DragonFlyBSD, FreeBSD 5.5, MidnightBSD 0.1-CURRENT before 20061115, NetBSD-current before 20061116, NetBSD-4 before 20061203, and TrustedBSD, allows local users to read arbitrary memory contents via certain negative values of crom_buf->len in an FW_GCROM command. NOTE: this issue has been labeled as an integer overflow, but it is more like an integer signedness error.

## Which versions are affected by CVE-2006-6013?

It affects 5 products.


Products: Dragonflybsd Dragonflybsd, Freebsd Freebsd, Midnightbsd Midnightbsd, Netbsd Netbsd, Trustedbsd Trustedbsd.

## How do I fix CVE-2006-6013?

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

## Is CVE-2006-6013 being exploited?

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

## Other vulnerabilities in Freebsd Freebsd

- [CVE-2005-0708](https://insights.sbomify.com/CVE-2005-0708/): Information disclosure in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6013 and fix it if it is affected.

What it is: CVE-2006-6013 is a low-severity vulnerability in Freebsd Freebsd, published on 21 Nov 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-6013 in the wild and no public exploit code.

Affected product: Freebsd Freebsd. 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-2006-6013/ (Markdown: https://insights.sbomify.com/CVE-2006-6013/index.md)
```

## Sources

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

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