dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2025-2098

HIGH · 8.4 CVSS v4.0 Published 2025-03-26
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
Fast CAD Reader application 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 Fast CAD Reader in possibly all versions since the vendor has not responded to our messages. The tested version was 4.1.5

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

Fast CAD Reader on macOS is installed with overly permissive file permissions (rwxrwxrwx/777), allowing any user or process to modify the application's dynamic library files. This enables Dylib Hijacking where attackers can inject malicious code that executes with the application's elevated privileges, leading to privilege escalation.

MitigationCorrect file permissions on the Fast CAD Reader application directory to follow macOS best practices (e.g., drwxr-xr-x), then reinstall or patch the application to prevent Dylib Hijacking attacks.

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 Fast CAD Reader installation
    Open Terminal and run: find /Applications -iname '*fast*cad*' -o -iname '*cad*reader*' 2>/dev/null | head -20
    Affected if No Fast CAD Reader installation is found (not affected)
  2. Verify application bundle permissions
    For each found application, run: ls -la "/path/to/Fast CAD Reader.app/Contents/MacOS/" to list files and their permissions
    Affected if Any file or directory shows rwxrwxrwx (777) permissions, indicating world-writable access
  3. Check dynamic library permissions
    Run: find "/path/to/Fast CAD Reader.app" -name '*.dylib' -exec ls -la {} \; to inspect all dylib file permissions
    Affected if Any .dylib file has rwxrwxrwx (777) permissions, allowing injection of malicious code
  4. Inspect framework permissions if present
    Run: find "/path/to/Fast CAD Reader.app" -name '*.framework' -exec ls -la {} \; to check framework bundle permissions
    Affected if Any framework shows rwxrwxrwx (777) permissions on files within it
  5. Compare against expected secure permissions
    Secure applications should have 755 (rwxr-xr-x) or 644 (rw-r--r--) for files, 755 for directories. Run: stat -f '%OLp %N' /path/to/Fast\ CAD\ Reader.app/Contents/MacOS/*
    Affected if The permission octal codes are 777 (rwxrwxrwx) instead of 755 or 644

You are affected if Fast CAD Reader is installed and any of its files or dynamic libraries have overly permissive rwxrwxrwx (777) permissions that allow any local user to modify them.

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

Correct file permissions on the Fast CAD Reader application directory to follow macOS best practices (e.g., drwxr-xr-x), then reinstall or patch the application to prevent Dylib Hijacking attacks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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