CVSS: 9.8EPSS: 71%CPEs: 14EXPL: 0CVE-2018-7183
https://notcve.org/view.php?id=CVE-2018-7183
Buffer overflow in the decodearr function in ntpq in ntp 4.2.8p6 through 4.2.8p10 allows remote attackers to execute arbitrary code by leveraging an ntpq query and sending a response with a crafted array. Desbordamiento de búfer en la función decodearr en ntpq en ntp, desde la versión 4.2.8p6 hasta la 4.2.8p10, permite que atacantes remotos ejecuten código arbitrario aprovechando una consulta ntpq y enviando una respuesta con un array manipulado. • http://support.ntp.org/bin/view/Main/NtpBug3414 http://support.ntp.org/bin/view/Main/SecurityNotice#February_2018_ntp_4_2_8p11_NTP_S http://www.securityfocus.com/bid/103351 https://security.FreeBSD.org/advisories/FreeBSD-SA-18:02.ntp.asc https://security.gentoo.org/glsa/201805-12 https://security.netapp.com/advisory/ntap-20180626-0001 https://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbux03962en_us https://usn.ubuntu.com/3707-1 https://usn • CWE-787: Out-of-bounds Write •
CVSS: 9.8EPSS: 0%CPEs: 4EXPL: 0CVE-2018-6916
https://notcve.org/view.php?id=CVE-2018-6916
In FreeBSD before 11.1-STABLE, 11.1-RELEASE-p7, 10.4-STABLE, 10.4-RELEASE-p7, and 10.3-RELEASE-p28, the kernel does not properly validate IPsec packets coming from a trusted host. Additionally, a use-after-free vulnerability exists in the IPsec AH handling code. This issue could cause a system crash or other unpredictable results. En FreeBSD, en versiones anteriores a 11.1-STABLE, 11.1-RELEASE-p7, 10.4-STABLE, 10.4-RELEASE-p7 y 10.3-RELEASE-p28, el kernel no valida correctamente los paquetes IPsec provenientes de un host de confianza. Además, existe una vulnerabilidad de uso de memoria previamente liberada en el código de manipulación de IPsec AH. • http://www.securitytracker.com/id/1040460 https://www.freebsd.org/security/advisories/FreeBSD-SA-18:01.ipsec.asc • CWE-416: Use After Free •
CVSS: 3.3EPSS: 0%CPEs: 1EXPL: 0CVE-2017-1086
https://notcve.org/view.php?id=CVE-2017-1086
In FreeBSD before 11.1-STABLE, 11.1-RELEASE-p4, 11.0-RELEASE-p15, 10.4-STABLE, 10.4-RELEASE-p3, and 10.3-RELEASE-p24, not all information in the struct ptrace_lwpinfo is relevant for the state of any thread, and the kernel does not fill the irrelevant bytes or short strings. Since the structure filled by the kernel is allocated on the kernel stack and copied to userspace, a leak of information of the kernel stack of the thread is possible from the debugger. As a result, some bytes from the kernel stack of the thread using ptrace (PT_LWPINFO) call can be observed in userspace. En FreeBSD, en versiones anteriores a 11.1-STABLE, 11.1-RELEASE-p4, 11.0-RELEASE-p15, 10.4-STABLE, 10.4-RELEASE-p3 y 10.3-RELEASE-p24, no toda la información en el struct ptrace_lwpinfo es relevante para el estado de los hilos y el kernel no rellena los bytes no relevantes o cadenas cortas. Dado que la estructura que rellena el kernel se asigna a la pila del kernel y se copia al espacio de usuario, es posible que se produzca una fuga de información de la pila del kernel del hilo desde el depurador. • http://www.securityfocus.com/bid/101861 http://www.securitytracker.com/id/1039809 https://www.freebsd.org/security/advisories/FreeBSD-SA-17:08.ptrace.asc • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 3.3EPSS: 0%CPEs: 1EXPL: 0CVE-2017-1088
https://notcve.org/view.php?id=CVE-2017-1088
In FreeBSD before 11.1-STABLE, 11.1-RELEASE-p4, 11.0-RELEASE-p15, 10.4-STABLE, 10.4-RELEASE-p3, and 10.3-RELEASE-p24, the kernel does not properly clear the memory of the kld_file_stat structure before filling the data. Since the structure filled by the kernel is allocated on the kernel stack and copied to userspace, a leak of information from the kernel stack is possible. As a result, some bytes from the kernel stack can be observed in userspace. En FreeBSD en versiones anteriores a 11.1-STABLE, 11.1-RELEASE-p4, 11.0-RELEASE-p15, 10.4-STABLE, 10.4-RELEASE-p3 y 10.3-RELEASE-p24, el kernel no limpia correctamente la memoria de la estructura kld_file_stat antes de rellenar los datos. Dado que la estructura que rellena el kernel se asigna a la pila del kernel y se copia al espacio de usuario, es posible que se produzca una fuga de información desde la pila del kernel. • http://www.securityfocus.com/bid/101857 http://www.securitytracker.com/id/1039811 https://www.freebsd.org/security/advisories/FreeBSD-SA-17:10.kldstat.asc • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •
CVSS: 7.8EPSS: 0%CPEs: 1EXPL: 0CVE-2017-1087
https://notcve.org/view.php?id=CVE-2017-1087
In FreeBSD 10.x before 10.4-STABLE, 10.4-RELEASE-p3, and 10.3-RELEASE-p24 named paths are globally scoped, meaning a process located in one jail can read and modify the content of POSIX shared memory objects created by a process in another jail or the host system. As a result, a malicious user that has access to a jailed system is able to abuse shared memory by injecting malicious content in the shared memory region. This memory region might be executed by applications trusting the shared memory, like Squid. This issue could lead to a Denial of Service or local privilege escalation. En FreeBSD en versiones 10.x anteriores a 10.4-STABLE, 10.4-RELEASE-p3 y 10.3-RELEASE-p24, las rutas nombradas tienen alcance global, lo que significa que un proceso localizado en una jaula puede leer y modificar el contenido de los objetos de la memoria compartida de POSIX creados por un proceso en otra jaula o el sistema host. • http://www.securityfocus.com/bid/101867 http://www.securitytracker.com/id/1039810 https://www.freebsd.org/security/advisories/FreeBSD-SA-17:09.shm.asc • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •