CVE-2017-2675
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 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.
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 · moderate confidenceLittle Snitch installer versions 3.0-3.7.3 contain a local privilege escalation vulnerability in how it installs the LaunchDaemon configuration file 'at.obdev.littlesnitchd.plist' to /Library/LaunchDaemons. The vulnerability likely stems from improper permission handling or insecure file placement during installation, potentially allowing a local unprivileged user to manipulate the plist file and gain elevated privileges.
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= 3.0= 3.0.1= 3.0.2= 3.0.3= 3.0.4= 3.1= 3.1.1= 3.3= 3.3.1= 3.3.2= 3.3.3= 3.3.4= 3.6.2= 3.6.3= 3.6.4= 3.7= 3.7.1= 3.7.2= 3.7.3CVSS 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.0/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.
-
Identify installed Little Snitch versionOpen Little Snitch app and go to Little Snitch > About Little Snitch, or check /Applications for Little Snitch version infoAffected if Version is 3.0 through 3.7.3 (including 3.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.1, 3.1.1, 3.3, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.6.2, 3.6.3, 3.6.4, 3.7, 3.7.1, 3.7.2, or 3.7.3)
-
Verify LaunchDaemon plist existsRun: ls -la /Library/LaunchDaemons/at.obdev.littlesnitchd.plistAffected if File exists on the system
-
Check plist file ownershipRun: ls -l /Library/LaunchDaemons/at.obdev.littlesnitchd.plist and verify owner is root:wheelAffected if Owner is not root or group is not wheel, indicating potential manipulation
-
Check plist file permissionsRun: ls -l /Library/LaunchDaemons/at.obdev.littlesnitchd.plist and verify permissions are -rw-r----- (640) or stricterAffected if File has overly permissive access (world-readable or writable by non-root users)
-
Check plist file contents for suspicious entriesRun: sudo plutil -p /Library/LaunchDaemons/at.obdev.littlesnitchd.plist and examine ProgramArguments or Program path for unexpected valuesAffected if File contains unexpected program paths or arguments not matching known Little Snitch daemon configuration
User is affected if Little Snitch version is 3.0-3.7.3 AND the LaunchDaemon plist at /Library/LaunchDaemons/at.obdev.littlesnitchd.plist exists with incorrect ownership or overly permissive access rights.
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 dataUpgrade Little Snitch to a version newer than 3.7.3 to receive the patched installer. For existing installations, verify the integrity of /Library/LaunchDaemons/at.obdev.littlesnitchd.plist and ensure it has correct ownership and permissions.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2675 — 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-2017-2675 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