CVE-2025-8700: Privilege Escalation via get-task-allow entitlement in Invoice Ninja
Invoice Ninja's configuration on macOS, specifically the presence of entitlement "com.apple.security.get-task-allow", allows local attackers with unprivileged access (e.g. via a malicious application) to attach a debugger, read or modify the process memory, inject code in the application's context despite being signed with Hardened Runtime and bypass Transparency, Consent, and Control (TCC). Acquired resource access is limited to previously granted permissions by the user. Access to other resources beyond granted permissions requires user interaction with a system prompt asking for permission.
According to Apple documentation, when a non-root user runs an app with the debugging tool entitlement, the system presents an authorization dialog asking for a system administrator's credentials. Since there is no prompt when the target process has "get-task-allow" entitlement, the presence of this entitlement was decided to be treated as a vulnerability because it removes one step needed to perform an attack.
This issue was fixed in version 5.0.175
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-8700?
CVE-2025-8700 is rated as a high-severity vulnerability due to its potential for local attackers to exploit the entitlement and gain unauthorized access.
How do I fix CVE-2025-8700?
To fix CVE-2025-8700, ensure your Invoice Ninja application is updated to the latest version that addresses this vulnerability.
Who is affected by CVE-2025-8700?
CVE-2025-8700 affects users running Invoice Ninja on macOS with specific configuration settings that expose the application to potential attacks.
What types of attacks are possible with CVE-2025-8700?
CVE-2025-8700 allows local attackers to attach a debugger, read or modify process memory, and inject code into the Invoice Ninja application.
Is there a workaround for CVE-2025-8700?
Currently, the recommended approach is to implement security updates, as there are no known effective workarounds for CVE-2025-8700.