dbcve.org
Claris ProApplication · Claris

CVE-2023-42920

HIGH · 7.8 CVSS v3.1 Published 2024-03-19
Fix available
A fix is available. Upgrade to 20.2 or later.
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
Claris International has fixed a dylib hijacking vulnerability in the FileMaker Pro.app and Claris Pro.app versions on macOS.

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 · moderate confidence

This is a dylib hijacking vulnerability in FileMaker Pro.app and Claris Pro.app on macOS. Dylib hijacking occurs when an application loads a dynamic library from an insecure path, allowing an attacker to place a malicious library in a location where the application will load it instead of the legitimate one. This can lead to arbitrary code execution within the application's context.

MitigationApply the vendor-provided security update to FileMaker Pro.app and Claris Pro.app to address the dylib hijacking vulnerability.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Claris ProApplication
Affected:all versions
Filemaker ProApplication
Affected:< 20.2

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. Verify FileMaker Pro or Claris Pro installation
    Check /Applications folder for 'FileMaker Pro.app' or 'Claris Pro.app' bundle existence. Use command: ls -la /Applications/ | grep -i 'FileMaker\|Claris'
    Affected if Either FileMaker Pro.app or Claris Pro.app is present on the system
  2. Identify installed version of FileMaker Pro
    Right-click the app in /Applications, select 'Get Info', or run: defaults read /Applications/FileMaker\ Pro.app/Contents/Info.plist CFBundleShortVersionString
    Affected if Version is less than 20.2 (for FileMaker Pro)
  3. Identify installed version of Claris Pro
    Right-click the app in /Applications, select 'Get Info', or run: defaults read /Applications/Claris\ Pro.app/Contents/Info.plist CFBundleShortVersionString
    Affected if Any version is installed (Claris Pro has no fixed version threshold, all versions affected)
  4. Confirm dylib loading configuration exists
    Examine the application's Info.plist for LSRequireClassic or investigate the app bundle's MacOS/Frameworks directory for library loading directives. Use: ls -la /Applications/FileMaker\ Pro.app/Contents/
    Affected if The application bundle contains configuration that allows loading dylibs from insecure paths

User is affected if FileMaker Pro with version < 20.2 or any version of Claris Pro is installed and the application uses vulnerable dylib loading behavior.

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
Upgrade available Upgrade to 20.2 or later
Fixed in 20.2
Interim mitigation

Apply the vendor-provided security update to FileMaker Pro.app and Claris Pro.app to address the dylib hijacking vulnerability.

Fix this in Claris Pro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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