CVE-2020-3432 json
Cisco AnyConnect Secure Mobility Client for Mac OS File Corruption Vulnerability
published 2025-02-11 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2020-24703
- cvss
- 5.6
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
A 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.
Patch / fix
- cisco anyconnect_secure_mobility_client 4.9.00086
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 20 mo ago
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 5.6 | CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:H/E:X/RL:X/RC:X |
| CISA ADP | 3.1 | 5.6 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:H |
| CNA | 3.1 | 5.6 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:H |
| CNA | 3.0 | 5.6 | CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:H |
Affected products
- Cisco Cisco Secure Client
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
Sources
- CVE List CVE-2020-3432
- NVD CVE-2020-3432
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.