dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2025-1413

HIGH · 8.4 CVSS v4.0 Published 2025-02-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/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
DaVinci Resolve on MacOS was found to be installed with incorrect file permissions (rwxrwxrwx). This is inconsistent with standard macOS security practices, where applications should have drwxr-xr-x permissions. Incorrect permissions allow for Dylib Hijacking. Guest account, other users and applications can exploit this vulnerability for privilege escalation. This issue affects DaVinci Resolve on MacOS in versions before 19.1.3.

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

DaVinci Resolve on macOS is installed with world-writable permissions (rwxrwxrwx) instead of the standard macOS application permissions (drwxr-xr-x). This allows any user or process to modify the application's dynamic libraries, enabling Dylib hijacking for privilege escalation.

MitigationApply standard macOS permissions (755 / drwxr-xr-x) to the DaVinci Resolve application bundle and its contents, then verify the application functions correctly after the permission change.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Locate DaVinci Resolve installation
    Open Terminal and run: ls -la "/Applications/Blackmagic Design/" 2>/dev/null | grep -i davinci
    Affected if The DaVinci Resolve.app folder does not exist, meaning the application is not installed on this system
  2. Check DaVinci Resolve.app bundle permissions
    Run: stat -f "%A %OLp" "/Applications/Blackmagic Design/DaVinci Resolve.app" to view the permission bits in octal format (for example 755 or 777)
    Affected if The permissions display as 777 (rwxrwxrwx), indicating world-writable access instead of the standard macOS drwxr-xr-x (755)
  3. Inspect dynamic library permissions inside the bundle
    Run: find "/Applications/Blackmagic Design/DaVinci Resolve.app" -name "*.dylib" -exec stat -f "%A %OLp %N" {} \; to check the permission bits on all .dylib files
    Affected if Any .dylib files show 777 permissions, meaning they can be modified by any user or process on the system

If DaVinci Resolve is installed on macOS and the application bundle or any of its .dylib files have world-writable (777) permissions instead of the standard 755, the environment is vulnerable to Dylib hijacking for privilege escalation.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply standard macOS permissions (755 / drwxr-xr-x) to the DaVinci Resolve application bundle and its contents, then verify the application functions correctly after the permission change.

Recommended fix High confidence

DaVinci Resolve 19.1.3

  1. Backup all DaVinci Resolve projects and user preferences to a safe location
  2. Download DaVinci Resolve version 19.1.3 or later from the official Blackmagic Design website (https://www.blackmagicdesign.com/products/davinciresolve)
  3. Uninstall the existing DaVinci Resolve installation from the Applications folder
  4. Install the new version 19.1.3 or later by running the installer package
  5. Verify that the installed application has correct permissions (drwxr-xr-x) by checking the application bundle in /Applications

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1413 — 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-2025-1413 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