Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

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

36
Routine
MEDIUM 5.3REMOTEUPGRADE

CVE-2018-10470 is a medium-severity flaw (CVSS 5.3) affecting little snitch. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 dis

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.6% (top 49%)
CISA exploited listNo
WeaknessCWE-347
Published2018-06-12
Last modified2026-06-17
Publisher (CNA): Objective Development Software GmbH · Vendor: objective development

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

objective development little snitch UPGRADE
Affected: >= 4.0 and <= 4.0.6
Fixed in: newer than 4.0.6
Safe to downgrade to: a release before 4.0
1. Check installed version
apt-cache policy little-snitch || rpm -q little-snitch || little-snitch --version
2. UPGRADE to newer than 4.0.6 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade little-snitch
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade little-snitch
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.0 (Debian / Ubuntu)
apt-cache madison little-snitch sudo apt install little-snitch=<VERSION_BEFORE_4.0> sudo apt-mark hold little-snitch
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list little-snitch sudo dnf downgrade little-snitch-<VERSION_BEFORE_4.0> sudo dnf versionlock add little-snitch
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-10470?

little snitch: upgrade to newer than 4.0.6. Exact commands for each OS are on this page.

Is CVE-2018-10470 being exploited?

CVE-2018-10470 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-10470 affect?

CVE-2018-10470 affects little snitch. Severity is medium (CVSS 5.3). 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 cra

How urgent is CVE-2018-10470?

Priority 36/100. Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.