Apple patched critical flaws in macOS Monterey but not in Big Sur nor Catalina

About 35-40% of iGiant's desktop OS installs potentially vulnerable, says Intego

Apple last week patched two actively exploited vulnerabilities in macOS Monterey yet has left users of older supported versions of its desktop operating system unprotected.

In a blog post on Tuesday, security biz Intego said fixes applied to address CVE-2022-22675 (AppleAVD bug) and CVE-2022-22674 (Intel Graphics Driver bug) in macOS Monterey were not backported to macOS Big Sur or macOS Catalina.

The AppleAVD issue is unpatched for macOS Big Sur, said Joshua Long, chief security analyst for Intego, while Catalina isn't affected because it lacks the AppleAVD component for decoding audio and video. The Intel Graphics Driver flaw, he said, looks like it affects both Big Sur and Catalina.

This is the first time since the release of macOS Monterey that Apple has neglected to patch actively exploited vulnerabilities for Big Sur and Catalina

"This is the first time since the release of macOS Monterey that Apple has neglected to patch actively exploited vulnerabilities for Big Sur and Catalina," said Long. "The previous three actively exploited vulnerabilities were each patched simultaneously for Monterey, Big Sur, and Catalina."

Apple did not respond to a request to explain why it has left older macOS installations without updates for these particular issues.

Apple's macOS Monterey debuted on October 25, 2021, and is the most recent macOS release. macOS Big Sur was released on November 12, 2020, and was last updated March 14, 2022. Its predecessor, macOS Catalina was released October 7, 2019, and also saw its most recent update on March 14, 2022.

Unlike Microsoft, which publishes its Windows Lifecycle Policy, Apple details hardware obsolescence dates but offers no written commitment covering its macOS support policy. In recent times, the iBiz has supported its active macOS release for a year while also publishing updates and security patches for its previous two macOS releases.

Support for macOS Catalina is expected to end around November 2022, and macOS Big Sur's retirement date looks to be, more or less, November 2023.

According to Long, 35-40 per cent of Macs currently in use are vulnerable to one or both of these bugs.

Apple emits macOS, iOS, iPadOS patches for 'exploited' security bugs


Long says that security researcher Mickey Jin has confirmed that M1-based Macs running macOS Big Sur are vulnerable to the AppleAVD bug (CVE-2022-22675), as are devices running iOS 14 and iPadOS 14, which Apple stopped supporting in January.

CVE-2022-22675 is an out-of-bounds write bug and could allow arbitrary code execution with kernel privileges.

As for the Intel Graphics bug (CVE-2022-22674), Long says Intego is working to confirm Big Sur and Catalina are affected, but said that's been difficult to establish because the out-of-bounds read vulnerability – which could allow reading kernel memory – was reported by an anonymous researcher.

But he said, "we have high confidence that CVE-2022-22674 likely affects both macOS Big Sur and macOS Catalina," because nearly every vulnerability in the Intel Graphics Driver component in recent years has affected all versions of macOS.

Long added that there are dozens of other vulnerabilities in Big Sur and Catalina that are not being actively exploited.

"Apple has an unfortunate history of knowingly leaving 'supported' macOS versions unprotected from some in-the-wild, actively exploited attacks," he said. "This type of scenario where a vendor chooses not to release a patch is sometimes referred to as a 'perpetual zero-day.'" ®

Other stories you might like

  • Pentester pops open Tesla Model 3 using low-cost Bluetooth module
    Anything that uses proximity-based BLE is vulnerable, claim researchers

    Tesla Model 3 and Y owners, beware: the passive entry feature on your vehicle could potentially be hoodwinked by a relay attack, leading to the theft of the flash motor.

    Discovered and demonstrated by researchers at NCC Group, the technique involves relaying the Bluetooth Low Energy (BLE) signals from a smartphone that has been paired with a Tesla back to the vehicle. Far from simply unlocking the door, this hack lets a miscreant start the car and drive away, too.

    Essentially, what happens is this: the paired smartphone should be physically close by the Tesla to unlock it. NCC's technique involves one gadget near the paired phone, and another gadget near the car. The phone-side gadget relays signals from the phone to the car-side gadget, which forwards them to the vehicle to unlock and start it. This shouldn't normally happen because the phone and car are so far apart. The car has a defense mechanism – based on measuring transmission latency to detect that a paired device is too far away – that ideally prevents relayed signals from working, though this can be defeated by simply cutting the latency of the relay process.

    Continue reading
  • Google assuring open-source code to secure software supply chains
    Java and Python packages are the first on the list

    Google has a plan — and a new product plus a partnership with developer-focused security shop Snyk — that attempts to make it easier for enterprises to secure their open source software dependencies.

    The new service, announced today at the Google Cloud Security Summit, is called Assured Open Source Software. We're told it will initially focus on some Java and Python packages that Google's own developers prioritize in their workflows. 

    These two programming languages have "particularly high-risk profiles," Google Cloud Cloud VP and GM Sunil Potti said in response to The Register's questions. "Remember Log4j?" Yes, quite vividly.

    Continue reading
  • Rocket Lab is taking NASA's CAPSTONE to the Moon
    Mission to lunar orbit is further than any Photon satellite bus has gone before

    Rocket Lab has taken delivery of NASA's CAPSTONE spacecraft at its New Zealand launch pad ahead of a mission to the Moon.

    It's been quite a journey for CAPSTONE [Cislunar Autonomous Positioning System Technology Operations and Navigation Experiment], which was originally supposed to launch from Rocket Lab's US launchpad at Wallops Island in Virginia.

    The pad, Launch Complex 2, has been completed for a while now. However, delays in certifying Rocket Lab's Autonomous Flight Termination System (AFTS) pushed the move to Launch Complex 1 in Mahia, New Zealand.

    Continue reading

Biting the hand that feeds IT © 1998–2022