Four-Byte Write and Timing Bug Let Researchers Run Code in Windows SmartScreen Enclave
Security researchers ran their own code inside a protected part of Windows that is meant to stay sealed off even when the rest of the computer is taken over. The protected area is a VBS enclave, an isolated slice of memory the operating system uses to guard secrets, and the one they broke into handles passwords for a Windows anti-phishing feature. The work was done in a lab as a proof of
Se muestra el contenido original; la traduccion localizada aun no esta disponible.
Qué ocurrió
Security researchers ran their own code inside a protected part of Windows that is meant to stay sealed off even when the rest of the computer is taken over. The protected area is a VBS enclave, an isolated slice of memory the operating system uses to guard secrets, and the one they broke into handles passwords for a Windows anti-phishing feature. The work was done in a lab as a proof of
Por que importa
The development may change operating conditions or market expectations around Security. Further confirmation and measurable outcomes matter.
Entidades afectadas
Ver evidencia
1 articulos · 1 informe original · 1 independientes
- The Hacker NewsFuente primaria · Respalda · EN · 100%Four-Byte Write and Timing Bug Let Researchers Run Code in Windows SmartScreen Enclave ↗
Afirmaciones
- Four-Byte Write and Timing Bug Let Researchers Run Code in Windows SmartScreen Enclave Observado
Conflictos
No se detectaron conflictos importantes en la evidencia disponible.
Cronología
- Primera publicación
Movimiento del mercado posterior al evento
La reacción del mercado aún no está disponible para este activo y periodo.