# CVE-2017-3813: Privilege escalation in Cisco AnyConnect Secure Mobility Client Software for Windows Versions prior to released versions 4.4.00243 and later and 4.3.05017 and later.

> Local attackers can exploit insufficient access controls in the SBL module to launch Internet Explorer with SYSTEM privileges, enabling privileged command execution.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v2w8-r4gc-fv4c

## What is CVE-2017-3813?

CVE-2017-3813 is a high-severity vulnerability in Cisco Anyconnect Secure Mobility Client, published on 9 Feb 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the Start Before Logon (SBL) module of Cisco AnyConnect Secure Mobility Client Software for Windows could allow an unauthenticated, local attacker to open Internet Explorer with the privileges of the SYSTEM user. The vulnerability is due to insufficient implementation of the access controls. An attacker could exploit this vulnerability by opening the Internet Explorer browser. An exploit could allow the attacker to use Internet Explorer with the privileges of the SYSTEM user. This may allow the attacker to execute privileged commands on the targeted system. This vulnerability affects versions prior to released versions 4.4.00243 and later and 4.3.05017 and later. Cisco Bug IDs: CSCvc43976.

Weakness: CWE-862 (Missing Authorization), CWE-264

## Which versions are affected by CVE-2017-3813?

It affects 1 product.


Products: Cisco Anyconnect Secure Mobility Client.

## How do I fix CVE-2017-3813?

No fix has been published for CVE-2017-3813 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-3813 being exploited?

There is no known exploitation of CVE-2017-3813 in the wild and no public exploit code.

Public exploit code:

- Cisco AnyConnect Secure Mobility Client 4.3.04027 - Local Privilege Escalation (exploitdb)

## Other vulnerabilities in Cisco Anyconnect Secure Mobility Client

- [CVE-2020-3433](https://insights.sbomify.com/CVE-2020-3433/): Cisco AnyConnect Secure Mobility Client for Windows DLL Hijacking (high 7.8, exploited in the wild)
- [CVE-2020-3153](https://insights.sbomify.com/CVE-2020-3153/): Cisco AnyConnect Secure Mobility Client for Windows Uncontrolled Search Path (medium 6.5, exploited in the wild)
- [CVE-2012-3088](https://insights.sbomify.com/CVE-2012-3088/): Security feature bypass in n/a (critical 9.3)
- [CVE-2012-2493](https://insights.sbomify.com/CVE-2012-2493/): Code injection in n/a (critical 9.3)
- [CVE-2011-2040](https://insights.sbomify.com/CVE-2011-2040/): Code injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3813 and fix it if it is affected.

What it is: CVE-2017-3813 is a high-severity vulnerability in Cisco Anyconnect Secure Mobility Client, published on 9 Feb 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-3813 in the wild and no public exploit code.

Affected product: Cisco Anyconnect Secure Mobility Client. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-3813/ (Markdown: https://insights.sbomify.com/CVE-2017-3813/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-3813
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-3813
- OSV: https://osv.dev/vulnerability/CVE-2017-3813

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-3813/
Summaries are generated and may contain mistakes; the official description above is the record.