home.social

#cve202321716 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cve202321716, aggregated by home.social.

fetched live
  1. Four months later on CVE-2023-21716 - I still haven't seen a single in the wild document that reaches RCE for this, nor an RCE exploit.

    #CVE202321716

  2. Four months later on CVE-2023-21716 - I still haven't seen a single in the wild document that reaches RCE for this, nor an RCE exploit.

    #CVE202321716

  3. Four months later on CVE-2023-21716 - I still haven't seen a single in the wild document that reaches RCE for this, nor an RCE exploit.

    #CVE202321716

  4. Four months later on CVE-2023-21716 - I still haven't seen a single in the wild document that reaches RCE for this, nor an RCE exploit.

    #CVE202321716

  5. Haven't seen any working exploitation of #CVE202321716 at all - all just people reusing the crash POC, nobody made it to RCE.

  6. Haven't seen any working exploitation of #CVE202321716 at all - all just people reusing the crash POC, nobody made it to RCE.

  7. Haven't seen any working exploitation of #CVE202321716 at all - all just people reusing the crash POC, nobody made it to RCE.

  8. Haven't seen any working exploitation of #CVE202321716 at all - all just people reusing the crash POC, nobody made it to RCE.

  9. I've been keeping an eye on #CVE202321716 (the MS Word RTF vuln) via #GossiMonitoring

    The headline is, people are starting to experiment with it.

  10. I've been keeping an eye on #CVE202321716 (the MS Word RTF vuln) via #GossiMonitoring

    The headline is, people are starting to experiment with it.

  11. I've been keeping an eye on #CVE202321716 (the MS Word RTF vuln) via #GossiMonitoring

    The headline is, people are starting to experiment with it.

  12. I've been keeping an eye on #CVE202321716 (the MS Word RTF vuln) via #GossiMonitoring

    The headline is, people are starting to experiment with it.

  13. Keep an eye on CVE-2023-21716 aka MS Word vulnerability from February 2023 in RTF files.

    There's a public proof of concept: qoop.org/publications/cve-2023

    Where it gets more interesting - you can embed RTF files in email, Microsoft Outlook renders them with no clicks, by just reading the email. There's a decent chance this could become problematic combination.. although not yet as the PoC is vague enough to require a clue to exploit. HT @fellows

    #CVE202321716

  14. Keep an eye on CVE-2023-21716 aka MS Word vulnerability from February 2023 in RTF files.

    There's a public proof of concept: qoop.org/publications/cve-2023

    Where it gets more interesting - you can embed RTF files in email, Microsoft Outlook renders them with no clicks, by just reading the email. There's a decent chance this could become problematic combination.. although not yet as the PoC is vague enough to require a clue to exploit. HT @fellows

    #CVE202321716

  15. Keep an eye on CVE-2023-21716 aka MS Word vulnerability from February 2023 in RTF files.

    There's a public proof of concept: qoop.org/publications/cve-2023

    Where it gets more interesting - you can embed RTF files in email, Microsoft Outlook renders them with no clicks, by just reading the email. There's a decent chance this could become problematic combination.. although not yet as the PoC is vague enough to require a clue to exploit. HT @fellows

    #CVE202321716

  16. Keep an eye on CVE-2023-21716 aka MS Word vulnerability from February 2023 in RTF files.

    There's a public proof of concept: qoop.org/publications/cve-2023

    Where it gets more interesting - you can embed RTF files in email, Microsoft Outlook renders them with no clicks, by just reading the email. There's a decent chance this could become problematic combination.. although not yet as the PoC is vague enough to require a clue to exploit. HT @fellows

    #CVE202321716