Latest Security Update for Mojave forbids WebKit from working

Privacy & Security General
TCMfan OP
Created Mar ’20
Replies 4
Boosts 0
Views 2.8k
Participants 3

I installed the latest beta Security Update for macOS Mojave and now everything WebKit fails:

error 21:49:46.890449 -0600 sandboxd Sandbox: com.apple.WebKit(2027) deny(1) process-info-pidinfo self

Violation: deny(1) process-info-pidinfo self

Process: com.apple.WebKit [2027]

Path: /System/Library/StagedFrameworks/Safari/WebKit.framework/Versions/A/XPCServices/com.apple.WebKit.WebContent.xpc/Contents/MacOS/com.apple.WebKit.WebContent

Load Address: 0x105eb8000

Identifier: com.apple.WebKit.WebContent

Version: 14609.1.20.111.8 (14609)

Build Info: 59-WebKit2~7609001020111008

Code Type: x86_64 (Native)

Parent Process: launchd [1]

Responsible: /Applications/Safari.app/Contents/MacOS/Safari [1948]

User ID: 501



Date/Time: 2020-03-31 21:49:46.869 MDT

OS Version: Mac OS X 10.14.6 (18G5006)

Report Version: 8


MetaData: {"uid":501,"platform_binary":"yes","target-pid":2027,"target-name":"com.apple.WebKit","signing-id":"com.apple.WebKit.WebContent","operation":"process-info-pidinfo","primary-filter-value":2027,"primary-filter":"target","platform-policy":false,"platform-binary":true,"summary":"deny(1) process-info-pidinfo self","process":"com.apple.WebKit","errno":1,"target":2027,"process-path":"\/System\/Library\/StagedFrameworks\/Safari\/WebKit.framework\/Versions\/A\/XPCServices\/com.apple.WebKit.WebContent.xpc\/Contents\/MacOS\/com.apple.WebKit.WebContent","action":"deny","profile-flags":2,"flags":5,"responsible-process-path":"\/Applications\/Safari.app\/Contents\/MacOS\/Safari","responsible-process-pid":1948,"build":"Mac OS X 10.14.6 (18G5006)","profile-in-collection":false,"pid":2027,"hardware":"Mac"}



Thread 0 (id: 32154):

0 libsystem_kernel.dylib 0x00007fff7d7dee0a __proc_info + 10

1 CoreFoundation 0x00007fff51704885 ____CFRunLoopSetOptionsReason_block_invoke_2 + 240

2 libdispatch.dylib 0x00007fff7d65c63d _dispatch_client_callout + 8

3 libdispatch.dylib 0x00007fff7d65dd4b _dispatch_once_callout + 20

4 CoreFoundation 0x00007fff516ef426 __CFRunLoopSetOptionsReason + 4171

5 LaunchServices 0x00007fff52cab072 _LSApplicationCheckIn + 6630

6 HIServices 0x00007fff4fe6f85e _RegisterApplication + 6201

7 WebKit 0x0000000106329a86 WebKit::WebProcess::initializeProcessName(WebKit::AuxiliaryProcessInitializationParameters const&) + 18

8 WebKit 0x0000000105f37eb0 WebKit::AuxiliaryProcess::initialize(WebKit::AuxiliaryProcessInitializationParameters const&) + 122

9 WebKit 0x0000000105ed3610 WebContentServiceInitializer + 491

10 WebKit 0x00000001060b03d9 invocation function for block in WebKit::XPCServiceEventHandler(NSObject<OS_xpc_object>*) + 434

11 libxpc.dylib 0x00007fff7d8ddeec _xpc_connection_call_event_handler + 56

12 libxpc.dylib 0x00007fff7d8dbe82 _xpc_connection_mach_event + 933

13 libdispatch.dylib 0x00007fff7d65c6dd _dispatch_client_callout4 + 9

14 libdispatch.dylib 0x00007fff7d6710d6 _dispatch_mach_msg_invoke + 436

15 libdispatch.dylib 0x00007fff7d662792 _dispatch_lane_serial_drain + 268

16 libdispatch.dylib 0x00007fff7d671c19 _dispatch_mach_invoke + 481

17 libdispatch.dylib 0x00007fff7d66754b _dispatch_main_queue_callback_4CF + 813

18 CoreFoundation 0x00007fff516a9ca6 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9

19 CoreFoundation 0x00007fff516a93d3 __CFRunLoopRun + 2300

20 CoreFoundation 0x00007fff516a8885 CFRunLoopRunSpecific + 459

21 Foundation 0x00007fff5392b2af -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 280

22 Foundation 0x00007fff5392b184 -[NSRunLoop(NSRunLoop) run] + 76

23 libxpc.dylib 0x00007fff7d8e205b _xpc_objc_main + 552

24 libxpc.dylib 0x00007fff7d8e1b5d _xpc_copy_xpcservice_dictionary + 0

25 WebKit 0x00000001060ad7c7 WebKit::XPCServiceMain(int, char const**) + 547

26 libdyld.dylib 0x00007fff7d6a93d5 start + 1

27 com.apple.WebKit.WebContent 0x0000000000000001



Thread 1 (id: 32161):

0 libsystem_kernel.dylib 0x00007fff7d7dfbfa __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff7d89c3fd start_wqthread + 13

2 0x00001239000186a9



Thread 2 (id: 32162):

0 libsystem_kernel.dylib 0x00007fff7d7dfbfa __workq_kernreturn + 10

1 libsystem_pthread.dylib 0x00007fff7d89c3fd start_wqthread + 13



Thread 3 (id: 32163, JavaScriptCore bmalloc scavenger):

0 libsystem_kernel.dylib 0x00007fff7d7e1866 __psynch_cvwait + 10

1 libc++.1.dylib 0x00007fff7a8e3b31 std::__1::condition_variable::__do_timed_wait(std::__1::unique_lock<std::__1::mutex>&, std::__1::chrono::time_point<std::__1::chrono::system_clock, std::__1::chrono::duration<long long, std::__1::ratio<1l, 1000000000l> > >) + 93

2 JavaScriptCore 0x000000064ca7b396 bmalloc::Scavenger::threadRunLoop() + 758

3 JavaScriptCore 0x000000064ca7ad69 bmalloc::Scavenger::threadEntryPoint(bmalloc::Scavenger*) + 9

4 JavaScriptCore 0x000000064ca7d4e7 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (*)(bmalloc::Scavenger*), bmalloc::Scavenger*> >(void*) + 39

5 libsystem_pthread.dylib 0x00007fff7d89d2eb _pthread_body + 126

6 libsystem_pthread.dylib 0x00007fff7d8a0249 _pthread_start + 66

7 libsystem_pthread.dylib 0x00007fff7d89c40d thread_start + 13



Binary Images:

0x105eb8000 - 0x105eb8fff com.apple.WebKit.WebContent (14609 - 14609.1.20.111.8) <de8e2e85-325c-3a7d-a8e3-cefa000eecc4> /System/Library/StagedFrameworks/Safari/WebKit.framework/Versions/A/XPCServices/com.apple.WebKit.WebContent.xpc/Contents/MacOS/com.apple.WebKit.WebContent

0x105ec2000 - 0x1065b4fff com.apple.WebKit (14609 - 14609.1.20.111.8) <d3e2b5cc-3ac5-3cc7-ac28-c00dbe0abbb2> /System/Library/StagedFrameworks/Safari/WebKit.framework/Versions/A/WebKit

0x64babc000 - 0x64cb87ff3 com.apple.JavaScriptCore (14609 - 14609.1.20.111.8) <d086231e-dea4-3126-84bb-203dffd634bb> /System/Library/StagedFrameworks/Safari/JavaScriptCore.framework/Versions/A/JavaScriptCore

0x7fff4fe6c000 - 0x7fff4febeff7 com.apple.HIServices (1.22) <2be461ff-80b9-30d3-a574-aed5724b1c1b> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices

0x7fff5166e000 - 0x7fff51ab4ff7 com.apple.CoreFoundation (6.9 - 1575.231) <98542162-490b-35f9-a178-85b529bb2271> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation

0x7fff52c8a000 - 0x7fff52e3bff7 com.apple.LaunchServices (946 - 946) <a0c91634-9410-38e8-bc11-7a5a369e6ba5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices

0x7fff5390f000 - 0x7fff53cbcffb com.apple.Foundation (6.9 - 1575.231) <1a7f3800-dd05-3ee4-b27a-f7d1a1cca648> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation

0x7fff7a8db000 - 0x7fff7a92eff7 libc++.1.dylib (400.9.4) <9a60a190-6c34-339f-bb3d-aace942009a4> /usr/lib/libc++.1.dylib

0x7fff7d659000 - 0x7fff7d692ff7 libdispatch.dylib (1008.270.1) <97273678-e94c-3c8c-89f6-2e2020f4b43b> /usr/lib/system/libdispatch.dylib

0x7fff7d693000 - 0x7fff7d6bfff7 libdyld.dylib (655.1.1) <002418cc-ad11-3d10-865b-015591d24e6c> /usr/lib/system/libdyld.dylib

0x7fff7d7dd000 - 0x7fff7d805ff7 libsystem_kernel.dylib (4903.278.30) <59846671-384f-302b-9dc1-074829ce71eb> /usr/lib/system/libsystem_kernel.dylib

0x7fff7d89a000 - 0x7fff7d8a4ff7 libsystem_pthread.dylib (330.250.2) <2d5c08ff-484f-3d59-9132-ce1dcb3f76d7> /usr/lib/system/libsystem_pthread.dylib

0x7fff7d8d1000 - 0x7fff7d900fff libxpc.dylib (1336.261.4) <7a9d1bf7-f17f-3b87-9373-b0079544e8c5> /usr/lib/system/libxpc.dylib

Can this easily be resolved?

Replies  4
Boosts  0
Views  2.8k
Participants  3
Uli Fischer OP
Apr ’20

I have the same problem. Did you find a solution ?

Greetings Uli

0
TCMfan OP
Apr ’20

Unfortunately no; I am hoping they will release a new seed of the update this week that will fix this.


Everyone I know that has applied this update has been stuck in the same situation.


The one good thing is at least for web browsing, in addition to third party browsers, Safari Technology Preview can be installed and will work properly.


However, if you want to check your email, you have to run Thunderbird or some other client.


Update:
I think I might have a guess at this:
I installed the latest Safari 13.1.1 beta, which contains a new version of WebKit, and it continues to be slammed down by SIP.
However, Safari Technology Preview continues to work.
What I'm thinking is:

Failing versions of WebKit:
14609 (14609.1.20.111.8)
14609 (14609.2.3)
Working version in Safari Technology Preview:
14610.1.8.3
This makes me think the Sandbox rules that give permissions to WebKit version 14609 were broken by the Security Update.


0
haodo OP
Apr ’20

Same issue here on MacBook Pro with macOS Mojave version 10.14.6 (18G5006) after the Mojave security update. Both Safari and Mail can't load still. On my other machine running macOS Catalina version 10.15.5 Beta (19F53f) with Safari 13.1 (15609.2.1) and Mail 13.4 (3608.80.23.2.2) loads with no security issue.


I tried reinstalling the macOS Mojave and for a few days, everything was running. Eventually the WebKit apps gets blocked again from loading. I guess I could use csrutil in Recovery mode, but I'd rather just use Safari Tech Preview for now.

0
TCMfan OP
Apr ’20

Fixed in the latest version of the patch that updates macOS to 10.14.6 (18G5015), released today (April 16, 2020.)

0
Latest Security Update for Mojave forbids WebKit from working
First post date Last post date
 
 
Q