Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-2675: Little Snitch version 3.0 through 3.7.3 suffer from a local privilege escalation vulnerability in the installe

33
Routine
HIGH 7.8DOWNGRADEDOWNGRADE

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

Little Snitch version 3.0 through 3.7.3 suffer from a local privilege escalation vulnerability in the installer part. The vulnerability is related to the installation of the configuration file "at.obdev.littlesnitchd.plist" which gets installed to /Library/LaunchDaemons.

Why this priority

  • High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score7.8 (High)
Attack vectorLocal
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.3% (top 77%)
CISA exploited listNo
Published2017-04-06
Last modified2026-06-17
Publisher (CNA): Objective Development Software GmbH · Vendor: obdev · 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

obdev little snitch DOWNGRADE
Affected: 3.0 · 3.0.1 · 3.0.2 · 3.0.3 · 3.0.4 · 3.1 · 3.1.1 · 3.3
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.0
1. Check installed version
apt-cache policy little-snitch || rpm -q little-snitch || little-snitch --version
2. No fixed release: DOWNGRADE to a release before 3.0 (Debian / Ubuntu)
apt-cache madison little-snitch sudo apt install little-snitch=<VERSION_BEFORE_3.0> sudo apt-mark hold little-snitch
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list little-snitch sudo dnf downgrade little-snitch-<VERSION_BEFORE_3.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.
objective development little snitch DOWNGRADE
Affected: 3.6.2 · 3.6.3 · 3.6.4 · 3.7 · 3.7.1 · 3.7.2 · 3.7.3
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.6.2
1. Check installed version
apt-cache policy little-snitch || rpm -q little-snitch || little-snitch --version
2. No fixed release: DOWNGRADE to a release before 3.6.2 (Debian / Ubuntu)
apt-cache madison little-snitch sudo apt install little-snitch=<VERSION_BEFORE_3.6.2> sudo apt-mark hold little-snitch
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list little-snitch sudo dnf downgrade little-snitch-<VERSION_BEFORE_3.6.2> 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-2017-2675?

little snitch: downgrade or apply the listed mitigation; little snitch: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-2675 being exploited?

CVE-2017-2675 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-2017-2675 affect?

CVE-2017-2675 affects little snitch, little snitch. Severity is high (CVSS 7.8). Little Snitch version 3.0 through 3.7.3 suffer from a local privilege escalation vulnerability in the installer part. The vulnerability is related to the installation of the configuration file "at.obdev.littlesnitchd.plist" which gets insta

How urgent is CVE-2017-2675?

Priority 33/100. High severity

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.