TunnelblickApplication · Google

CVE-2012-3484

HIGH · 7.2 CVSS v2.0 Published 2012-08-26
Fix available
A fix is available. Upgrade to after 3.3beta20 or later.
See remediation →
77/100
Remediation priority · High
No privileges Zero-click

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 · unedited
Tunnelblick 3.3beta20 and earlier relies on a test for specific ownership and permissions to determine whether a program can be safely executed, which allows local users to bypass intended access restrictions and gain privileges via a (1) user-mountable image or (2) network share.

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 confidence

Tunnelblick versions 3.3beta20 and earlier contain a privilege escalation vulnerability where the application relies on filesystem ownership and permissions checks to determine if a program can be safely executed. Local users can bypass these checks by using user-mountable images or network shares to place executables in locations that satisfy the ownership/permission tests but are under user control, allowing arbitrary code execution with elevated privileges.

MitigationUpgrade Tunnelblick to a version newer than 3.3beta20. Additionally, restrict local users' ability to mount images or control network shares on systems running vulnerable Tunnelblick versions to limit attack surface.

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
TunnelblickApplication
Affected:<= 3.3beta20

CVSS 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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Tunnelblick version
    On macOS, open Terminal and run: ls /Applications/ | grep -i tunnelblick to find the app, then right-click Tunnelblick.app > Show Package Contents, and check Contents/Info.plist for CFBundleShortVersionString or CFBundleVersion, or use: defaults read /Applications/Tunnelblick.app/Contents/Info.plist CFBundleShortVersionString
    Affected if The version is 3.3beta20 or earlier (any version <= 3.3beta20)
  2. Verify Tunnelblick is configured to launch helper tools
    Check if Tunnelblick has any VPN configurations loaded or if it uses the 'launch-at-login' or helper tool features. Look in ~/Library/Application Support/Tunnelblick/ for configuration files (.tblk folders)
    Affected if Tunnelblick has active VPN configurations and is configured to manage connections, which triggers the vulnerable code path for executing helper tools
  3. Identify locations where unprivileged users can mount images or control shares
    Check if any non-admin users have privileges to mount disk images: dscl . -read /Users/username SecondaryGroupID or check /etc/auto_master for automount configurations that might allow user-controlled network shares
    Affected if Non-admin users can mount disk images (via hdiutil) or have write access to network share mount points that Tunnelblick might check for executable ownership

A user is affected if they are running Tunnelblick version 3.3beta20 or earlier AND have active VPN configurations that trigger the application's helper tool execution with elevated privileges, especially on systems where unprivileged users can mount disk images or control network share locations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 3.3beta20
Interim mitigation

Upgrade Tunnelblick to a version newer than 3.3beta20. Additionally, restrict local users' ability to mount images or control network shares on systems running vulnerable Tunnelblick versions to limit attack surface.

Fix this in Tunnelblick Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-3484 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-3484 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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