LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10470: Little Snitch versions 4.0 to 4.0.6 use the SecStaticCodeCheckValidityWithErrors() function without the kSe...

Little 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

Little Snitch 4.0 through 4.0.6 could misreport code-signing status for specially crafted macOS fat binaries. The main business risk is mistaken trust in an application’s signature, not confirmed remote compromise or privilege escalation from the provided sources.

Executive priority

Handle through normal endpoint hygiene. Prioritize remediation where Little Snitch trust indicators influence security decisions, but the supplied evidence does not justify emergency response.

Technical view

The issue is improper certificate/signature validation: Little Snitch used SecStaticCodeCheckValidityWithErrors() without kSecCSCheckAllArchitectures, so not all architectures in a fat binary were validated. This could create inconsistent reporting between the running process and the on-disk binary.

Likely exposure

Exposure is limited to macOS systems running Objective Development Little Snitch versions 4.0 to 4.0.6. Organizations without those versions are not affected based on the supplied evidence.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public exploit use, or weaponized exploitation. The described impact is user confusion around code-signature validity.

Researcher notes

This is CWE-347 tied to incomplete validation of multi-architecture macOS binaries. The key research question is whether signature-status inconsistency could affect policy enforcement, not just UI interpretation; the provided description only confirms confusion risk.

Mitigation direction

  • Inventory endpoints for Little Snitch 4.0 through 4.0.6.
  • Check Objective Development guidance for fixed or supported versions.
  • Upgrade or replace affected Little Snitch installations according to vendor guidance.
  • Review endpoint software trust decisions that depend on code-signing display status.

Validation and detection

  • Confirm installed Little Snitch versions on managed macOS endpoints.
  • Verify affected versions are no longer present after remediation.
  • Review vendor advisory details for the exact fixed-version boundary.
  • Check security tooling for alerts involving unsigned or suspicious macOS fat binaries.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-347: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-10470 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Objective Development Software GmbHLittle Snitch4.0 - 4.0.6Listed
Weakness

CWE details

CWE-347

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-347 · source CWE mapping

Improper Verification of Cryptographic Signature

Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs