17 ms·
About the security content of macOS Monterey 12.1
- xyst 5y agoSo many RCEs in this release. Apple used to be so smug about not being vulnerable in those 2000s commercials. Now that they have reached critical mass, their OS is equivalent to Windows.
- dt2m 5y agoThought the exact same thing. Karma's a bitch...
- Maursault 5y ago> their OS is equivalent to Windows. Yeah, they're basically identical, except macOS doesn't even have Defender.
- skoskie 5y agoMac keeps a list of (hashes of) apps that are not allowed to run. It’s updated constantly and synced to your computer, so in effect they can remotely disable malicious software for all users all at once. This was a big deal a few years ago when (IIRC) a bug caused it not to cache the list long enough and it started causing problems when it couldn’t phone home. Aside from that it’s always been a perfectly seamless process.
- newaccount74 5y ago> Mac keeps a list of (hashes of) apps that are not allowed to run. That's the XProtect blocklist, it's been around pretty long and hasn't caused any issues that I'm aware of. > bug caused it not to cache the list long enough and it started causing problems when it couldn’t phone home What changed is that since Catalina macOS additionally makes a synchronous check the first time you open an app. For certain things that are not code signed (eg. shell scripts), it checks every time. This can cause multi-second delays when launching apps or executing commands in the shell. (see https://sigpipe.macromates.com/2020/macos-catalina-slow-by-design/ https://sigpipe.macromates.com/2020/macos-catalina-slow-by-d...) To my knowledge, this issue has not been fixed and is still a problem in Monterey (first time app launches on my M1 Max sometimes take several seconds). It's possible to deactivate the check for Terminal (by marking it as a "Developer Tool" using a checkbox that sometimes shows up in System preferences, and sometimes doesn't). I'm not aware of a way to avoid this slowdown in Finder without disconnecting from the internet.
- Canada 5y agoI wonder how many of those bugs will be fixed in previous versions.
- cientifico 5y agoI wonder how many bugs they are aware and decide not to report.
- Turing_Machine 5y agoApple normally continues issuing security updates (but not necessarily fixing other bugs) for around 2 years after a new version of macOS has been released, though I don't believe they've ever formally specified that in writing. Monterey was released on October 25, 2021, so Big Sur should keep getting security updates until October 2023 or so. More than one version back is generally considered unsupported, I believe. I see a Big Sur update dated December 13, so it's definitely still being supported. While I haven't done an exhaustive check, it looks like it patches many of the same security holes. https://support.apple.com/en-us/HT212979 https://support.apple.com/en-us/HT212979
- howinteresting 5y agoThis is what Apple wants you to believe. In reality, Apple routinely skips security patches on older versions: https://www.vice.com/en/article/93bw8y/google-caught-hackers-using-a-mac-zero-day-against-hong-kong-users https://www.vice.com/en/article/93bw8y/google-caught-hackers... The only way to be safe on Apple's computers (and phones) is to update to the latest version the day it comes out.
- Turing_Machine 5y agoErr... that article explicitly says that the hole was in fact patched on Catalina, and it even has a link to the notice. https://support.apple.com/en-us/HT212825 https://support.apple.com/en-us/HT212825
- 5y ago
- WatchDog 5y agoCan't find any details on CVE-2021-30939, but the apple description sounds pretty bad.
- shrimpx 5y agoAlso multiple “arbitrary code execution” vulnerabilities if you play crafted audio files.
- deleted 5y ago[deleted]
- sumedh 5y agoI see lot of corporations whose employees are getting the credit, so does that mean the bounty goes to the employee or the corporation or its shared?
- eru 5y agoI would assume it depends on your employment contract?
- cyounkins 5y ago7 vulnerabilities with impact "may be able to execute arbitrary code with kernel privileges" :-( Are these things in Objective-C or Swift? Does Swift memory management make buffer overflows and use-after-free mistakes harder to make?
- fay59 5y agoThere is no Swift or Objective-C in the xnu kernel, so the answer to the first question has to be "no". To the second question, Swift is generally safe against these bugs except (1) in the face of race conditions and (2) when the developer uses things that have "unsafe" in the name.
- d1str0 5y agoIts probably less to do with buffer overflows and use-after-free of these applications, and more to do with the underlying OS APIs, and I assume most of the OS is still C, C++ and Obj-C.
- pjmlp 5y agoYes, Swift is memory safe in this regard (as long as Unsafe.... isn´t being used), however most code on macOS is still mostly C, C++ and Objective-C.
- guessbest 5y agoObjC and Swift are just application level programming languages. The XNU system kernel for macOS is written in mostly C with some C++. Anyway Swift is written in C++ last I checked and ObjC is a superset of C anyway. Everything done with ObjC can be done in C if the developer is feeling adventurous enough. https://github.com/apple/darwin-xnu https://github.com/apple/darwin-xnu C 82.5% C++ 8.7% Python 2.3% Roff 2.3% Assembly 1.4% HTML 1.1% Other 1.7%
- alwillis 5y agoRegarding WebKit, where there are several CVEs, is written in C++.
- bilkow 5y agoApple should keep providing security updates for the latest version supported on any machine. There are lots of macs stuck at macOS High Sierra (the last one that supports GPUs without metal), and none of them are receiving any security update.
- rubyist5eva 5y agoApple doesn't support software - they support hardware. When they stop supporting a particular piece of hardware, you're SOL.
- sroussey 5y agoI have a machine still rockin MacOS 9. No security updates either, though also not much of a target…
- grishka 5y agoAnd any app can run arbitrary code with kernel privileges by design.
- GhettoComputers 5y agoDid anything bad happen?
- grishka 5y agoI haven't ever used classic Mac OS when it was current, and I don't know anyone who did, but I do remember Windows 9x crashing and locking up being an almost daily occurrence. PCs came with dedicated reset buttons for a reason!
- GhettoComputers 5y agoI did, it was all intranet, I mentioned this in another post, but they didn't have the same threats as we do today. >PCs came with dedicated reset buttons for a reason! They still do! Windows 9x did suck, Windows NT however was amazing, it is like the most Linux like of all the Windows. How could they release Windows ME...
- AceJohnny2 5y agoI'm seeing 42 CVEs, of those, 24 are solved at a foundational level by memory-safe languages (I'm talking out-of-bounds, use-after-free, race conditions/locking issues) I wonder how long the same story will repeat before the balance shifts in favor of just rewriting in more modern languages. It's expensive work with a long ROI, but sounds like a lot of these are in foundational libraries that you want to be robust in the long run.
- varenc 5y agoIsn't Swift, which came from Apple, memory-safe in a single thread environment? It can't prevent data races at compile time like Rust, but I thought it was far safer in practice than C/C++/ObjC where I suspect all these vulns originate.
- grishka 5y agoSwift is their "user-facing" language because this trendy stuff with "smart" languages is apparently very important for PR. I would be surprised if most of the OS itself is written in something other than C/C++/ObjC.
- smilespray 5y agoI take it you're not a big fan of Swift, but there's little need to veer over into borderline conspiracy theories. I do think Apple is honestly committed to Swift over the long term, but it takes loads of time and care to replace the foundations of a building that's in daily use.
- grishka 5y agoI'm not a fan of these "smart" languages in general. I'm one of those who believes that the syntax of the language itself should be dumb, but all the smarts should be in the standard library. Like in Java for example. It's much easier to reason about what the code actually does when the language is dumb and calls into its standard library are explicit. It's bad when some benign-looking syntactic constructs trigger some kind of complex behavior. They might be committed to it, but I'm doubtful that it's at all possible to write e.g. parts of the kernel in it. And maybe, just maybe, they should direct all their efforts toward rewriting the OS in a safer language instead of making their UIs uglier with nonsensical paddings and messy-looking icons that pretend that there's no pixel grid.
- Rebelgecko 5y agoI'm still a few OS releases behind so I'm not used to paying attention to updates, but does this seem like an atypically high amount of RCEs?
- saagarjha 5y agoNope, they all have this many :)
- GhettoComputers 5y agoWhat do you upgrade for? Using Mac for music production means never updating immediately, and maybe not at all.
- Rebelgecko 5y agoI use the Nvidia GPU drivers, so I'll upgrade if Apple ever agrees to sign Nvidia's binaries for new OS releases (fat chance!)
- GhettoComputers 5y agohttp://dosdude1.com/mojave/ http://dosdude1.com/mojave/ just posted this if you're interested, never thought I'd suggest hackintosh resources to a Mac user, but if you need any of those new features: https://www.tonymacx86.com/nvidia-drivers https://www.tonymacx86.com/nvidia-drivers
- Lammy 5y ago> never thought I'd suggest hackintosh resources to a Mac user The first generation Mac Pros (2006/2007, with 32-bit EFI) are like this too and need to be basically hackintoshed to boot Mac OS X 10.8 and later: https://forums.macrumors.com/threads/2006-2007-mac-pro-1-1-2-1-and-os-x-el-capitan.1890435/ https://forums.macrumors.com/threads/2006-2007-mac-pro-1-1-2...
- GhettoComputers 5y ago
- GhettoComputers 5y agoAnyone tried this before to patch older OSX? PCs are more open so I assumed (correctly) this would exist. http://dosdude1.com/mojave/ http://dosdude1.com/mojave/
- noduerme 5y agoFor a company that demanded Flash be verboten because of the constant security threat, that's a whole lotta arbitrary code execution in webkit. Hey guys, you can't run this VM in our browser. Tell you what, let's just make our browser do everything it does. We won't run into any problems, I mean, everything's sandboxed right?
- GhettoComputers 5y agoWhy doesn't this work, does their sandbox suck? Qubes os seems to do it fine.
- my123 5y agoQubes uses a VM (without GPU acceleration in most scenarios) as the isolation boundary. That has performance and usability downsides… The sandbox keeps being tightened each release.
- GhettoComputers 5y agoVM performance is excellent, and has been so for about a decade, heres a recent thread with VFIO for GPU passthrough and VM (basically performance difference is negligible). https://old.reddit.com/r/VFIO/comments/n3mjj3/native_vs_vm_benchmarks_using_passthrough_for_gpu/ https://old.reddit.com/r/VFIO/comments/n3mjj3/native_vs_vm_b...
- my123 5y ago> GPU passthrough That’s just not an option for a regular phone or laptop, which is most of Apple’s market. Don’t forget about the RAM pressure too.
- GhettoComputers 5y ago>That’s just not an option for a regular phone or laptop, which is most of Apple’s market. Lots of Macs have more than one video card. I disagree, I mentioned it since they make their own silicon, and can do virtual GPU, memory management for the browser would be an issue, but Apple doesn't care, they just use swap on the SSD and it would still be cool to have that as an option for single tabs. All web browsing is just a huge amount of javascript virtual machines, and they have custom hardware to run it faster, they might do it via hardware, all their sandboxing is just OS based, TouchID ran its own OS and took years to crack, and needs hardware tools to do so.
- oger 5y agoWhy is Apple referencing CVE-2021-30938 and CVE-2021-30987 in their listing of security updates when they are not searchable in the National Vulnerability Database? Their status there is listed as "* REJECT * DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by the CVE program. Notes: none.". Can anyone give more clarity what is going on?
- directionless 5y agoSee comment https://news.ycombinator.com/item?id=29551572 https://news.ycombinator.com/item?id=29551572
- antihero 5y agoHas Monterey been fine for app/pods/React Native development so far? I swear every time I do a big update it takes ages to get the dev experience working again and I can't afford to lose time this close to Christmas with deadlines looming.
- TheRealSteel 5y agoThis frustrated me so much I've given up on the Mac. Bought a Dell this week. Actually quite excited to dive properly into Linux.
- GhettoComputers 5y agoSame for music production plugins.
- e40 5y agoI learned long ago to stay 1 release behind. I update to the latest just before a new one is released. This has served me very well for the last 5 years.
- mahrain 5y agoApple has been providing security updates for iOS 14, but so far no 14.8.2, strange since all other supported OS-es were updated today. Often the samen CVE’s get fixed in macOS, iOS, tvOS etc together. They are pushing iOS 15.2 though. I wonder if that means EOL for iOS 14?
- lgvln 5y agoThere have been no clarity on the status of “being able to stay on iOS 14”. Previously, you could stay on iOS 14.8.1 and the system saw it as “fully updated” but with the option to upgrade to iOS 15. Now, any devices with Automatic Updates turned on gets updated to iOS 15 automatically. I figure they allowed users to stay on iOS 14 in order to avoid the CSAM (legitimate concern) but now they are steamrolling everyone to iOS 15. Does that mean they will be removing CSAM in the future? I will wait for a couple of days to see if 14.8.2 or 14.9 appears. If it does not, I think we can consider iOS to be EOL (and that Apple changed their mind about iOS 14).
- terracatta 5y agoHi CEO of Kolide here and one of the reporters of CVE-2021-30987. This vulnerability is basically an information disclosure issue that enables you to get BSSIDs from the Airport Utility without the appropriate location tracking entitlement. Even worse the OS will not even flash the "location being accessed" indicator in the status bar when geolocation is determined this way. Essentially any app can shell out to the CLI tool and parse its output and then feed the resulting BSSID to one of the many external BSSID -> Geolocation services and determine a device's location. At Kolide we are huge believers that device geolocation should not be accessible to third party programs without end-user prompting (even ones managed by MDM) so we aggressively seek out gaps the TCC authorization model (or other OS issues that undermine the tenets of https://honest.security https://honest.security) and report them whenever we find them. I reported this vulnerability on January 17th 2020. Edit: Btw, I am not really sure why the CVE was withdrawn. To me this is a pretty serious information disclosure style vulnerability and everyone should upgrade to this release as soon as possible.
- oger 5y agoThis - again - lowers my confidence in the CVE mechanism... Thanks though for your background information what is / was going on!
- api 5y agoIt's 2021 and the list is still full of memory bounds checking errors.
- est31 5y agoApple, and most other companies in the industry, are still writing code in languages that don't have implicit bounds checking. Let alone all the code that they have written years ago that they still keep deploying. Nobody is going to rewrite that mountain in Rust any time soon.