2026-09-25 11:17 UTC
Replies (2)
-
@notbobbytables@infosec.exchange 2026-09-25 11:39
@vmcall@infosec.exchange I was surprised to learn that they apparently do not consider filename leakage from inaccessible directories across users as a problem. As a user and as an application programmer, I would like to be explicitly warned that filenames should not contain sensitive information, even if other users do not have the permission to list the content of the directory the file is in.
-
@david_chisnall@infosec.exchange 2026-09-26 08:14
@vmcall@infosec.exchange @notbobbytables@infosec.exchange When we did the ThunderClap attacks (ring-0 arbitrary-code execution by plugging something into the Thunderbolt port), the response from the Windows team was that it was out of scope for their threat model. The response from the OS X team was to tighten IOMMU permissions and to rearrange the mbuf structure so that the part exposed for DMA doesn’t contain pointers. The worst that we could do after that was corrupt data being loaded to the buffer cache from the disk if we forged the PCIe identifier and timed it exactly right (and somehow knew the physical address that was being written to and when), and that was closed by subsequent iterations of the hardware.