A Kernel Hacker Meets Fuchsia OS

Re:A Kernel Hacker Meets Fuchsia OS by kernal on Wednesday May 25, 2022 @11:13AM (#31505723)

>Very nice right up on how unfinished and insecure Fuchsia is as a result of it being so unfinished.

Did you even read the write up? The only bug found was the ability to read the kernel log. Everything else was manufactured.

[ Parent | on HN ]

Re:A Kernel Hacker Meets Fuchsia OS by binkHN on Wednesday May 25, 2022 @11:37AM (#31506068)

You’re kidding right? Did you miss the parts about KASLR being broken and syscalls with TODOs for missing validations? And the CVEs created in relation to these?

[ Parent | on HN ]

Re:A Kernel Hacker Meets Fuchsia OS by kernal on Wednesday May 25, 2022 @12:22PM (#31506696)

I saw one CVE (CVE-2022-0882) for the innocuous kernel log bug. How many CVE's did you see? As for the KASLR, this was a known issue to the Fuchsia devs.

>This is a known-issue. KASLR support on the zircon kernel is just there so that it doesn't bit-rot. We are always picking up a static address instead of a dynamic one.

>Once physboot rollout is complete, that should make it easier to support kaslr.

[ Parent | on HN ]

Re:A Kernel Hacker Meets Fuchsia OS by staticassertion on Wednesday May 25, 2022 @11:54AM (#31506326)

KASLR is a pretty meh mitigation. But yeah, "todo" around capability checking probably should have been a higher priority fix.

[ Parent | on HN ]