Marc Newlin

Ocorre uma leitura fora dos limites devido a uma verificação de limites insuficiente. Esta falha permite que um dispositivo USB malicioso cause a terminação inesperada do sistema ou leia a memória do kernel, que é a área de memória central usada pelo sistema operacional para gerenciar hardware e processos.

Um problema de use-after-free existe devido ao gerenciamento inadequado de memória. Isso ocorre quando um programa continua a usar um ponteiro após ele ter sido liberado, o que pode levar à corrupção da memória do kernel ou ao encerramento inesperado do sistema.

Um problema de corrupção de memória existe devido à validação de entrada insuficiente. Um invasor em proximidade física do dispositivo pode ser capaz de corromper a memória do processo.

Um problema de gerenciamento de sessões foi corrigido com verificações aprimoradas. Um invasor com acesso físico ao acessório pode ser capaz de extrair sua chave de emparelhamento Bluetooth e monitorar o tráfego Bluetooth. O problema está relacionado ao gerenciamento de sessões de usuário e pode ser explorado para obter acesso não autorizado ao tráfego Bluetooth.

O problema está relacionado a erros na representação de informações pela interface do usuário no Driver Bluetooth da Microsoft. Isso permite que um invasor remoto realize ataques de falsificação de identidade. A vulnerabilidade pode ser explorada para emparelhar um teclado Bluetooth virtual sem autenticação ou confirmação do usuário.

A critical Bluetooth security flaw could be exploited by threat actors to take control of Android, Linux, macOS, and iOS devices. The issue relates to a case of authentication bypass that enables attackers to connect to susceptible devices and inject keystrokes to achieve code execution as the victim. This could lead to remote escalation of privilege with no additional execution privileges needed, and user interaction is not required for exploitation. The estimated number of potentially affected devices worldwide is not specified, but the flaw affects multiple operating systems, including Android, Linux, macOS, and iOS.

The issue allows keystroke injection, bypassing encryption, and is also known as MouseJack.

The issue allows remote attackers to discover a CM MAC address by sniffing Wi-Fi traffic and performing simple arithmetic calculations.

The issue allows remote attackers to write arbitrary data to a known pathname, specifically /var/tmp/sess *, by leveraging the device's operation in UI dev mode.

The issue allows remote attackers to compute password-of-the-day values.

The issue allows remote attackers to discover a WAN IPv6 IP address by leveraging knowledge of the CM MAC address.

The issue allows remote attackers to access the web UI by establishing a session to the `wan0` WAN IPv6 address and then entering unspecified hardcoded credentials. This `wan0` interface cannot be accessed from the public Internet.

The issue allows configuration changes via CSRF, which can be exploited to make unauthorized changes to the device settings.

The issue allows configuration changes via CSRF, which can be exploited to make unauthorized changes to the device settings.

The Comcast firmware on the affected devices does not set the secure flag for cookies in an https session to an administration application. This makes it easier for remote attackers to capture these cookies by intercepting their transmission within an http session.

The issue concerns the absence of the HTTPOnly flag in a Set-Cookie header for administration applications. This omission makes it easier for remote attackers to obtain potentially sensitive information via script access to cookies.

The issue allows remote attackers to conduct successful forced-pairing attacks between an RF4CE remote and a set-top box by repeatedly transmitting the same pairing code.

The issue allows physically proximate attackers to read arbitrary files on the device. This can be achieved by pressing a specific sequence of buttons on an RF4CE remote to access the diagnostic display and then launching a Remote Web Inspector script.

The issue allows physically proximate attackers to access an SNMP server by connecting a cable to the Ethernet port and establishing communication with the device's link-local IPv6 address.

The issue allows physically proximate attackers to execute arbitrary commands as root. This can be achieved by accessing the diagnostics menu on the set-top box and then posting to a Web Inspector route.