• richmondez@lemdro.id
    link
    fedilink
    English
    arrow-up
    56
    arrow-down
    1
    ·
    21 hours ago

    This disclosure has been rushed for the views and hype IMO, none of the big distros had fixes ready to go on this this morning.

    • purplemonkeymad@programming.dev
      link
      fedilink
      English
      arrow-up
      11
      ·
      12 hours ago

      Yea I didn’t think the post was that professional. Also the “unminified” version is just the minified with more white space. It still has poor names and no explanation of the binary blob.

      • jj4211@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 hour ago

        Looking at the binary blob, it’s a payload to assume privileges as possible and exec sh. So replace su with that and the binary gets to use su’s filesystem privileges without needing access to actually write it.

        The vulnerability part is when the door opens to replace any file’s read cache with arbitrary content. The binary payload is just an obvious example of the sort of payload that could do a ton of damage.

    • ShortN0te@lemmy.ml
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      3
      ·
      11 hours ago

      The patches where proposed over a month ago and the patch to the kernel was commited on 1th of April.

      Either the Vulnerability was not proper communicated to the distro maintainers or they were the ones sleeping.

      This was probably executed as a responsible discllsure where clear timelines and release dates get communicated from the beginning.

      I find it hard to blame the security team here when there was 1 month of time between first commited patch and release of the PoC.