Show filters
531 Total Results
Displaying 311-320 of 531
Sort by:
Attacker Value
Unknown

CVE-2006-5550

Disclosure Date: October 26, 2006 (last updated October 04, 2023)
The kernel in FreeBSD 6.1 and OpenBSD 4.0 allows local users to cause a denial of service via unspecified vectors involving certain ioctl requests to /dev/crypto.
0
Attacker Value
Unknown

CVE-2006-5482

Disclosure Date: October 24, 2006 (last updated October 04, 2023)
ufs_vnops.c in FreeBSD 6.1 allows local users to cause an unspecified denial of service by calling the ftruncate function on a file type that is not VREG, VLNK or VDIR, which is not defined in POSIX.
0
Attacker Value
Unknown

CVE-2006-5483

Disclosure Date: October 24, 2006 (last updated October 04, 2023)
p1003_1b.c in FreeBSD 6.1 allows local users to cause an unspecified denial of service by setting a scheduler policy, which should only be settable by root.
0
Attacker Value
Unknown

CVE-2006-4516

Disclosure Date: October 12, 2006 (last updated October 04, 2023)
Integer signedness error in FreeBSD 6.0-RELEASE allows local users to cause a denial of service (memory corruption and kernel panic) via a PT_LWPINFO ptrace command with a large negative data value that satisfies a signed maximum value check but is used in an unsigned copyout function call.
0
Attacker Value
Unknown

CVE-2006-4172

Disclosure Date: September 26, 2006 (last updated October 04, 2023)
Integer overflow vulnerability in the i386_set_ldt call in FreeBSD 5.5, and possibly earlier versions down to 5.2, allows local users to cause a denial of service (crash) and possibly execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2006-4178.
0
Attacker Value
Unknown

CVE-2006-4178

Disclosure Date: September 26, 2006 (last updated October 04, 2023)
Integer signedness error in the i386_set_ldt call in FreeBSD 5.5, and possibly earlier versions down to 5.2, allows local users to cause a denial of service (crash) via unspecified arguments that use negative signed integers to cause the bzero function to be called with a large length parameter, a different vulnerability than CVE-2006-4172.
0
Attacker Value
Unknown

CVE-2006-4304

Disclosure Date: August 24, 2006 (last updated October 04, 2023)
Buffer overflow in the sppp driver in FreeBSD 4.11 through 6.1, NetBSD 2.0 through 4.0 beta before 20060823, and OpenBSD 3.8 and 3.9 before 20060902 allows remote attackers to cause a denial of service (panic), obtain sensitive information, and possibly execute arbitrary code via crafted Link Control Protocol (LCP) packets with an option length that exceeds the overall length, which triggers the overflow in (1) pppoe and (2) ippp. NOTE: this issue was originally incorrectly reported for the ppp driver.
0
Attacker Value
Unknown

CVE-2006-2655

Disclosure Date: June 02, 2006 (last updated October 04, 2023)
The build process for ypserv in FreeBSD 5.3 up to 6.1 accidentally disables access restrictions when using the /var/yp/securenets file, which allows remote attackers to bypass intended access restrictions.
0
Attacker Value
Unknown

CVE-2006-2654

Disclosure Date: June 02, 2006 (last updated October 04, 2023)
Directory traversal vulnerability in smbfs smbfs on FreeBSD 4.10 up to 6.1 allows local users to escape chroot restrictions for an SMB-mounted filesystem via "..\\" sequences. NOTE: this is similar to CVE-2006-1864, but this is a different implementation of smbfs, so it has a different CVE identifier.
0
Attacker Value
Unknown

CVE-2006-1056

Disclosure Date: April 20, 2006 (last updated October 04, 2023)
The Linux kernel before 2.6.16.9 and the FreeBSD kernel, when running on AMD64 and other 7th and 8th generation AuthenticAMD processors, only save/restore the FOP, FIP, and FDP x87 registers in FXSAVE/FXRSTOR when an exception is pending, which allows one process to determine portions of the state of floating point instructions of other processes, which can be leveraged to obtain sensitive information such as cryptographic keys. NOTE: this is the documented behavior of AMD64 processors, but it is inconsistent with Intel processors in a security-relevant fashion that was not addressed by the kernels.
0