# CVE-2015-7600: Privilege escalation in n/a

> Local attackers can escalate privileges by exploiting weak file permissions in the Cisco VPN Client configuration file.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 6 Oct 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x8rh-5gwj-qvc6

## What is CVE-2015-7600?

CVE-2015-7600 is a high-severity vulnerability in n/a, published on 6 Oct 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cisco VPN Client 5.x through 5.0.07.0440 uses weak permissions for vpnclient.ini, which allows local users to gain privileges by entering an arbitrary program name in the Command field of the ApplicationLauncher section.

Weakness: CWE-264

## Which versions are affected by CVE-2015-7600?

It affects 1 product.


Products: Cisco Vpn Client.

## How do I fix CVE-2015-7600?

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

## Is CVE-2015-7600 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1106](https://insights.sbomify.com/CVE-2002-1106/): Security feature bypass in n/a (high 7.5)
- [CVE-2002-1107](https://insights.sbomify.com/CVE-2002-1107/): Weak cryptography in n/a (high 7.5)
- [CVE-2006-2679](https://insights.sbomify.com/CVE-2006-2679/): Privilege escalation in n/a (high 7.2)
- [CVE-2002-1447](https://insights.sbomify.com/CVE-2002-1447/): Memory corruption in n/a (high 7.2)
- [CVE-2012-3052](https://insights.sbomify.com/CVE-2012-3052/): Privilege escalation in n/a (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-7600 and fix it if it is affected.

What it is: CVE-2015-7600 is a high-severity vulnerability in n/a, published on 6 Oct 2015. 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-2015-7600 in the wild and no public exploit code.

Affected product: n/a. 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-2015-7600/ (Markdown: https://insights.sbomify.com/CVE-2015-7600/index.md)
```

## Sources

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

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