• schizo@forum.uncomfortable.business
    link
    fedilink
    English
    arrow-up
    11
    ·
    1 month ago

    It’s serious, but seems like a wonky attack vector for most.

    Yeah, it’s super trivially exploited, BUT it requires you to do a series of dumb things or let an attacker have access to your LAN which is one of those you-have-bigger-problems moments anyways.

    And then you have to use their added printer (though there’s an exploit path that may be usable to over-write the printer you already have configured, if the attacker knows what that might be) to print something before anything happens.

    Dude who found it seems to have overhyped it just a little bit (while being a huge dick about it), but I could see how you might exploit this in certain circumstances.

    • atzanteol@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      12
      ·
      1 month ago

      This could be an issue on like a college campus or something. Under those circumstances one should definitely be running a host-based firewall though.

      • schizo@forum.uncomfortable.business
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 month ago

        Yeah, and at that point your network should be enforcing client isolation too, which is also a mitigation for this specific issue in large, shared networks like a college campus, or office, or public Wi-Fi at wherever.