How palmoff/fm_dylib_checker works
Project Type and Purpose
• This is a native macOS desktop application built with Xcode (Swift, Cocoa/AppKit).
• Purpose: scan installed FileMaker Pro runtimes/versions on the user’s Mac to detect known dylib hijack vulnerabilities and present the results in a GUI table.
File Structure
• Top-level Xcode project: FM_dylib_checker.xcodeproj contains build settings, schemes, workspace data.
• Source directory FM_dylib_checker/:
• AppDelegate.swift – application lifecycle
• ViewController.swift – main UI logic for scanning and displaying results
• Main.storyboard – UI layout (buttons, table view for output)
• FM_dylib_checker.entitlements – sandbox or file-access entitlements
• Release artifacts under release/ (built .dmg).
Additional Insights from README
• No external back-end: all scanning is done locally.
• Vulnerability rules are likely encoded in code (e.g., known version ranges, dylib names).
• User workflow: launch App → click “Scan” → see list of FileMaker installations and vulnerability status.
a. Main Components to Model
1. User Interface (ViewController, Storyboard)
2. Application Core / Scan Manager (Swift classes that enumerate FileMaker installs, apply vulnerability rules)
3. File System Access Layer (API calls to locate installed apps, read Info.plist or binary metadata)
4. Vulnerability Rules Module (hard-coded CVE logic or configuration resource)
6. (Optional) Logging/Error Handler
b. Relationships & Data Flow
• User clicks “Scan” (UI) → invokes Scan Manager
• Scan Manager queries File System Access Layer to locate installed FileMaker applications
• For each discovered app, pass its version and dylib list into the Vulnerability Rules Module
• Rules Module returns safe/unsafe status
• Scan Manager aggregates results and hands them to the Output Renderer
• UI displays the results; errors funnel back into a Logger/Error Handler and optionally to a popup alert
c. Architectural Patterns & Principles
• MVC (ViewController = Controller, Storyboard = View, Swift model classes = Model)
• Single monolithic desktop application (no microservices)
• Layered separation: UI layer, business logic layer, data access (file system) layer
d. Key Technologies & Frameworks
• Swift / Cocoa (AppKit)
• Foundation APIs for FileManager and Bundle inspection
• Storyboard and TableView (UI)
• macOS Sandbox entitlements (for file system access)