CVE-2018-10470
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 · uneditedLittle Snitch versions 4.0 to 4.0.6 use the SecStaticCodeCheckValidityWithErrors() function without the kSecCSCheckAllArchitectures flag and therefore do not validate all architectures stored in a fat binary. An attacker can maliciously craft a fat binary containing multiple architectures that may cause a situation where Little Snitch treats the running process as having no code signature at all while erroneously indicating that the binary on disk does have a valid code signature. This could lead to users being confused about whether or not the code signature is valid.
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 confidenceLittle Snitch 4.0-4.0.6 fails to properly validate code signatures in fat binaries because it calls SecStaticCodeCheckValidityWithErrors() without the kSecCSCheckAllArchitectures flag. This allows attackers to craft malicious multi-architecture fat binaries that cause Little Snitch to display contradictory states: showing no signature for the running process while indicating a valid signature exists for the binary on disk.
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>= 4.0, <= 4.0.6CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 Little Snitch is installedCheck for Little Snitch.app in /Applications or ~/Applications: ls -la "/Applications/Little Snitch.app" or ls -la "~/Applications/Little Snitch.app"Affected if Little Snitch.app does not exist in either location means not installed
-
Determine installed versionRun: defaults read "/Applications/Little Snitch.app/Contents/Info" CFBundleVersion or right-click Little Snitch.app > Get Info > VersionAffected if Version number cannot be determined or app not found
-
Compare version against affected rangeCompare the discovered version number to the affected range: 4.0 through 4.0.6. Versions below 4.0 or above 4.0.6 are not in the affected rangeAffected if Installed version is 4.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, or 4.0.6 means the environment is affected by this CVE
-
Verify Little Snitch code signature (optional verification)Run: codesign -dv "/Applications/Little Snitch.app" to verify the application itself is properly signedAffected if This check is informational only and does not indicate vulnerability status
If Little Snitch is installed and its version is 4.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, or 4.0.6, then the environment is affected by CVE-2018-10470 because the application lacks the kSecCSCheckAllArchitectures flag during code signature validation.
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 dataLittle Snitch should update to a version that applies the kSecCSCheckAllArchitectures flag when validating code signatures to ensure all architectures in fat binaries are properly verified.
- Consultation2.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,520.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10470 — 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-2018-10470 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