• Brewchin@lemmy.world
    link
    fedilink
    English
    arrow-up
    49
    ·
    2 days ago

    This was an interesting series of shorts. The bouncing screen edge overlay and the use of PDF made me chuckle. Very nostalgic.

    Thirty-odd years after it was first ejaculated into the world, PDF still remains the demon threat vector for payloads that just won’t die.

    • Carl@anarchist.nexus
      link
      fedilink
      English
      arrow-up
      17
      arrow-down
      2
      ·
      2 days ago

      I mean, following proper disclosure procedure requires giving the manufacturer adequate time to patch the vulnerabilities before they are released. Would you prefer they just publish the full how-to right up front, and create a zero-day for anyone (from script kiddies to state-sponsored hackers) to use as they see fit?

  • Forsho@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    2
    ·
    2 days ago

    fucking embedded pdfs. Is there any tool that can detect this shit in advance, idk like Kaspersky but for iphones.

    • KairuByte@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      2
      ·
      2 days ago

      Please don’t use Kaspersky.

      Also, no app would be able to do something like this unless it comes from Apple. Apps are sandboxed, they can’t peer into a different app, or the system itself.

        • KairuByte@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          19 hours ago

          If that is in fact how this works (I haven’t dug in too far) then technically yes. The problem is, these are one off zero days. You can’t exactly test that this problem exists unless you know it exists, and if you know it exists then Apple knows it exists (in the case of a mainstream antivirus app at least) so there’s no point in actually attempting to exploit it, just throw in a check for vulnerable versions.

          There’s no one size fits all “all pdf exploits that ever will exist” solution because there are exploits that will likely not exist for a time.