1. Forum
  2. Usenet
  3. COMP.SYS.MAC.SYSTEM

  • Incompetent Apple Safari QA shipped the SAME exploited severe bug three

    From Andy Burnelli@21:1/5 to All on Fri Jul 8 21:10:08 2022
    XPost: misc.phone.mobile.iphone

    The Apple QA team is so incompetent that they don't know the first thing
    about testing, which is that when you find and fix a bug, you put processes
    in place so that the same bug doesn't come back to bite you again.

    They shipped the bug in 2013 (Safari, iOS, iPadOS, and macOS).
    And then again in 2016 (Safari, iOS, iPadOS, and macOS).
    And yet again in 2022 (Safari, iOS, iPadOS, and macOS).

    Holy Christ. This is clear evidence of gross incompetence of Apple QA!

    Each time Apple shipped the _same_ bug, it was exploited in the wild.
    *That's how grossly incompetent Apple QA truly is*

    *Google Researchers Detail 5-Year-Old Apple Safari Vulnerability Exploited in the Wild*
    <https://thehackernews.com/2022/06/google-researchers-detail-5-year-old.html> --
    If Apple spent just some of their huge marketing budget in QA R&D, Apple wouldn't be such incompetent software coders who ship the same bug 3 times.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Andy Burnelli on Fri Jul 8 14:30:54 2022
    XPost: misc.phone.mobile.iphone

    On 2022-07-08 13:10, Andy Burnelli wrote:
    The Apple QA team is so incompetent that they don't know the first thing about testing, which is that when you find and fix a bug, you put processes in place so that the same bug doesn't come back to bite you again.

    They shipped the bug in 2013 (Safari, iOS, iPadOS, and macOS).
    And then again in 2016 (Safari, iOS, iPadOS, and macOS).
    And yet again in 2022 (Safari, iOS, iPadOS, and macOS).

    Holy Christ. This is clear evidence of gross incompetence of Apple QA!

    Each time Apple shipped the _same_ bug, it was exploited in the wild.
     *That's how grossly incompetent Apple QA truly is*

    *Google Researchers Detail 5-Year-Old Apple Safari Vulnerability
    Exploited in the Wild* <https://thehackernews.com/2022/06/google-researchers-detail-5-year-old.html>



    Wow. You don't even know how to read:

    '"In this case, the variant was completely patched when the
    vulnerability was initially reported in 2013," Maddie Stone of Google
    Project Zero said. "However, the variant was reintroduced three years
    later during large refactoring efforts. The vulnerability then continued
    to exist for 5 years until it was fixed as an in-the-wild zero-day in
    January 2022."'

    So 2013, 2016...

    ...and no "again in 2022".

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jerry@21:1/5 to Alan on Fri Jul 8 16:23:58 2022
    XPost: misc.phone.mobile.iphone

    On Fri, 8 Jul 2022 14:30:54 -0700, Alan wrote:

    So 2013, 2016...

    ...and no "again in 2022".

    Even worse then as that means it existed, was fixed, & then it was
    reintroduced & exploited in the wild undetected by Apple for five years.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Jerry on Sat Jul 9 12:51:59 2022
    XPost: misc.phone.mobile.iphone

    On 2022-07-08 16:23, Jerry wrote:
    On Fri, 8 Jul 2022 14:30:54 -0700, Alan wrote:

    So 2013, 2016...

    ...and no "again in 2022".

    Even worse then as that means it existed, was fixed, & then it was reintroduced & exploited in the wild undetected by Apple for five years.

    Or was utterly undetected in the wild as well...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jerry@21:1/5 to Alan on Sat Jul 9 14:52:41 2022
    XPost: misc.phone.mobile.iphone

    On Sat, 9 Jul 2022 12:51:59 -0700, Alan wrote:

    On 2022-07-08 16:23, Jerry wrote:
    On Fri, 8 Jul 2022 14:30:54 -0700, Alan wrote:

    So 2013, 2016...

    ...and no "again in 2022".

    Even worse then as that means it existed, was fixed, & then it was
    reintroduced & exploited in the wild undetected by Apple for five years.

    Or was utterly undetected in the wild as well...

    The bug was definitely exploited in the wild but that's not the bad part.

    What's worse is Apple re-introduced the same error twice and then never
    noticed it for five years until someone else had to tell Apple about it.

    That says a lot about how bad Apple is in their lack of testing processes.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)