3 ms·

About the security content of iOS 15.3.1 and iPadOS 15.3.1

• dlivingston 5y ago
  WebKit and buffer overflow vulnerabilities: name a more iconic duo
  • j_walter 5y ago
    Ace and Gary
  • syspec 5y ago
    Browsers are complicated - They all suffer from these kind of issues. Check the release notes for all of them and you'd see similar
    • pjmlp 5y ago
      They also share the implementation language that allows for such kind of bugs, so no wonder.
• keleftheriou 5y ago
  “Processing maliciously crafted web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been actively exploited.” Perhaps a WebKit monoculture isn’t such a great idea after all?
  • bzzzt 5y ago
    At least there's only 1 browser to fix on iOS. Where's the value of everyone switching to Google Chrome like I see with most Mac users? (except for Google and people who need support for some obscure CSS option immediately)
    • mikelpr 5y ago
      if there were other browser engines on iOS there'd also be only one browser to fix and it would be whichever had the bug since they don't share code and wouldn't share them bugs
    • aaaaaaaaata 5y ago
      This argument — here, again? Why did Microsoft base Edge on Chromium's open source foundation?
• pjmlp 5y ago
  > A use after free issue was addressed with improved memory management. Yet another one.