CVE-2006-6013

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.

2.1

CVSS

Severity: Low

CVSS 2.0 •

EPSS 0.08%

Vendor Advisory freebsd.org Vendor Advisory secunia.com Vendor Advisory kernelhacking.com

Affected: n/a n/a

References

Link	Tags
http://www.securityfocus.com/archive/1/451861/100/0/threaded	mailing list
http://securitytracker.com/id?1017344	vdb entry
http://archives.neohapsis.com/archives/fulldisclosure/2006-11/0261.html	mailing list
http://www.securityfocus.com/archive/1/451637/100/0/threaded	mailing list
http://mail-index.netbsd.org/tech-security/2006/11/16/0001.html	mailing list
http://security.freebsd.org/advisories/FreeBSD-SA-06:25.kmem.asc	vendor advisory
https://exchange.xforce.ibmcloud.com/vulnerabilities/30347	vdb entry
http://www.securityfocus.com/archive/1/452264/100/0/threaded	mailing list
http://www.securityfocus.com/archive/1/452331/100/0/threaded	mailing list
http://www.securityfocus.com/archive/1/452124/100/0/threaded	mailing list
http://mail-index.netbsd.org/tech-security/2006/12/14/0002.html	mailing list
http://www.dragonflybsd.org/cvsweb/src/sys/bus/firewire/fwdev.c
http://www.securityfocus.com/bid/21089	vdb entry
http://secunia.com/advisories/22917	third party advisory vendor advisory
http://www.securityfocus.com/archive/1/451698/100/0/threaded	mailing list
http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/ieee1394/fwdev.c
http://www.securityfocus.com/archive/1/451677/100/0/threaded	mailing list
http://www.securityfocus.com/archive/1/451629/100/0/threaded	mailing list
http://www.kernelhacking.com/bsdadv1.txt	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2006-6013?: CVE-2006-6013 has been scored as a low severity vulnerability.
How to fix CVE-2006-6013?: To fix CVE-2006-6013, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2006-6013 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2006-6013 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.