CVE-2020-3432
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 · uneditedA vulnerability in the uninstaller component of Cisco AnyConnect Secure Mobility Client for Mac OS could allow an authenticated, local attacker to corrupt the content of any file in the filesystem. The vulnerability is due to the incorrect handling of directory paths. An attacker could exploit this vulnerability by creating a symbolic link (symlink) to a target file on a specific path. A successful exploit could allow the attacker to corrupt the contents of the file. If the file is a critical systems file, the exploit could lead to a denial of service condition. To exploit this vulnerability, the attacker would need to have valid credentials on the system.Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.
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 confidenceThe vulnerability exists in the uninstaller component of Cisco AnyConnect Secure Mobility Client for Mac OS. An attacker with valid system credentials can exploit this by creating a symbolic link (symlink) to a target file, causing the uninstaller to corrupt that file's contents during its operation. This allows arbitrary file corruption on the local system, potentially leading to denial of service if critical system files are targeted.
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< 4.9.00086CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/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.
-
Check if Cisco AnyConnect is installed on Mac OSOpen Finder, navigate to /Applications folder, and look for 'Cisco AnyConnect Secure Mobility Client' or run: ls /Applications | grep -i anyconnectAffected if The application folder 'Cisco AnyConnect Secure Mobility Client' exists in /Applications
-
Identify the installed version of Cisco AnyConnectRight-click the application in /Applications, select 'Get Info', and note the version number under 'Version:', or run: defaults read /Applications/Cisco\ AnyConnect\ Secure\ Mobility\ Client.app/Contents/Info CFBundleShortVersionStringAffected if The displayed version number is lower than 4.9.00086 (for example: 4.8.0xxxx, 4.7.xxxx, etc.)
-
Verify the uninstaller component existsCheck for the uninstaller at /Applications/Cisco AnyConnect Secure Mobility Client/Uninstall AnyConnect.app or within the main application bundle under Contents/ResourcesAffected if The uninstaller application bundle is present on the system
-
Confirm the system is Mac OSClick the Apple menu (top-left), select 'About This Mac', or run: uname -s in TerminalAffected if The operating system is macOS (the vulnerability specifically affects the Mac OS uninstaller component)
If Cisco AnyConnect Secure Mobility Client is installed on Mac OS with a version lower than 4.9.00086, the environment is affected by this vulnerability.
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.
dbcve · scoped4.9.00086
Apply the Cisco software update that addresses this vulnerability. There are no available workarounds, so patching is the only remediation path.
4.9.00086 or later
- 1. Identify the current version of Cisco AnyConnect Secure Mobility Client installed on the system by checking the application or running 'vpn --version' in terminal
- 2. Navigate to the Cisco Software Download page (software.cisco.com) and locate the AnyConnect Secure Mobility Client for Mac OS
- 3. Download version 4.9.00086 or later for Mac OS
- 4. Uninstall the current version of AnyConnect from the system
- 5. Install the downloaded fixed version (4.9.00086 or later) following standard Cisco installation procedures
- 6. Verify the installation was successful by checking the installed version matches the fixed release
- 7. Restart the system if required by the installer
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3432 — 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-2020-3432 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