dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2024-9062

HIGH · 7.8 CVSS v3.1 Published 2025-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Archify application contains a local privilege escalation vulnerability due to insufficient client validation in its privileged helper tool, com.oct4pie.archifyhelper, which is exposed via XPC. Archify follows the "factored applications" model, delegating privileged operations—such as arbitrary file deletion and file permission changes—to this helper running as root. However, the helper does not verify the code signature, entitlements, or signing flags of the connecting client. Although macOS provides secure validation mechanisms like auditToken, these are not implemented. As a result, any local process can establish a connection to the helper and invoke privileged functionality, leading to unauthorized execution of actions with root-level privileges.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Archify application includes a privileged helper tool (com.oct4pie.archifyhelper) that runs as root and handles privileged operations like arbitrary file deletion and file permission changes. The helper exposes functionality via XPC but fails to validate the calling client's code signature, entitlements, or signing flags, and does not implement macOS secure validation mechanisms like auditToken. This allows any local process to connect to the helper and execute root-level operations.

MitigationImplement proper client validation in the privileged helper using auditToken to verify the connecting client's code signature, entitlements, and signing flags before allowing any privileged operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Archify application is installed
    Look for the Archify app in /Applications folder using Finder or run: ls -la /Applications/ | grep -i archify
    Affected if The Archify application exists in /Applications
  2. Locate the privileged helper tool binary
    Check for the helper in the system privileged helper directory: ls -la /Library/PrivilegedHelperTools/ | grep -i archify
    Affected if The file /Library/PrivilegedHelperTools/com.oct4pie.archifyhelper exists
  3. Check if the privileged helper is registered and running
    Run: sudo launchctl list | grep -i archify to see if the helper is loaded in launchd
    Affected if The com.oct4pie.archifyhelper service appears in the launchctl list output
  4. Verify the helper launchd configuration
    Check for the helper's launchd plist: ls -la /Library/LaunchDaemons/ | grep -i archify
    Affected if A plist file for com.oct4pie.archifyhelper exists in /Library/LaunchDaemons/
  5. Confirm helper executable permissions and ownership
    Run: ls -la /Library/PrivilegedHelperTools/com.oct4pie.archifyhelper and check if it is owned by root with executable permissions
    Affected if The helper binary exists, is owned by root, and has executable permissions

A user is affected if the Archify application is installed and the com.oct4pie.archifyhelper privileged helper tool exists and is registered with launchd, as this configuration allows any local process to trigger the vulnerable XPC interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper client validation in the privileged helper using auditToken to verify the connecting client's code signature, entitlements, and signing flags before allowing any privileged operations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9062 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data