CVE-2022-25366
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 · uneditedCryptomator through 1.6.5 allows DYLIB injection because, although it has the flag 0x1000 for Hardened Runtime, it has the com.apple.security.cs.disable-library-validation and com.apple.security.cs.allow-dyld-environment-variables entitlements. An attacker can exploit this by creating a malicious .dylib file that can be executed via the DYLD_INSERT_LIBRARIES environment variable.
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 confidenceCryptomator through 1.6.5 has insecure entitlements that enable dylib injection. Although Hardened Runtime is enabled (flag 0x1000), the combination of com.apple.security.cs.disable-library-validation and com.apple.security.cs.allow-dyld-environment-variables entitlements allows attackers to inject malicious .dylib files via the DYLD_INSERT_LIBRARIES environment variable.
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<= 1.6.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Cryptomator is installedSearch for Cryptomator in /Applications folder, or run: mdfind kMDItemCFBundleIdentifier == 'org.cryptomator.desktop' or ls /Applications | grep -i cryptomatorAffected if Cryptomator is found on the system
-
Determine installed Cryptomator versionRun: defaults read /Applications/Cryptomator.app/Contents/Info.plist CFBundleShortVersionString, or right-click Cryptomator.app > Get Info > VersionAffected if Version is 1.6.5 or lower
-
Locate the entitlements fileThe entitlements file is located at: /Applications/Cryptomator.app/Contents/CodeResources (for packaged app) or check the source if building from source. The file is typically named Cryptomator.entitlements in the project.Affected if Entitlements file exists
-
Inspect entitlements for vulnerable keysOpen the entitlements file and search for: com.apple.security.cs.disable-library-validation and com.apple.security.cs.allow-dyld-environment-variables. If using plist format, run: defaults read /path/to/Cryptomator.entitlements com.apple.security.cs.disable-library-validationAffected if Either com.apple.security.cs.disable-library-validation or com.apple.security.cs.allow-dyld-environment-variables is present and set to true
A user is affected if Cryptomator version 1.6.5 or lower is installed AND the application's entitlements file contains either the com.apple.security.cs.disable-library-validation or com.apple.security.cs.allow-dyld-environment-variables entitlement.
Generated from the published advisory. Verify against your own configuration.
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 dataRemove the com.apple.security.cs.disable-library-validation and com.apple.security.cs.allow-dyld-environment-variables entitlements from the application's entitlements file and rebuild the application, or upgrade to version 1.7.0 or later where these insecure entitlements have been removed.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25366 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-25366 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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