# CVE-2006-6308: Privilege escalation in n/a

> Local users can escalate privileges by stopping a process and launching a browser with elevated rights via the system tray.

- **Severity:** Medium 4.3 (`AV:L/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wvv9-x8pf-57jq

## What is CVE-2006-6308?

CVE-2006-6308 is a medium-severity vulnerability in n/a, published on 6 Dec 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Symantec LiveState 7.1 Agent for Windows allows local users to gain privileges by stopping the shstart.exe process and open "Web Self-Service" from the system tray icon, which will open a browser window running with elevated privileges.  NOTE: several third-party researchers have noted that administrator privileges may be necessary to terminate shstart.exe. If this is the case, then no privilege escalation occurs, and this is not a vulnerability

## Which versions are affected by CVE-2006-6308?

It affects 1 product.


Products: Symantec Livestate Agent for Windows.

## How do I fix CVE-2006-6308?

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

## Is CVE-2006-6308 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6308 and fix it if it is affected.

What it is: CVE-2006-6308 is a medium-severity vulnerability in n/a, published on 6 Dec 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-6308 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-2006-6308/ (Markdown: https://insights.sbomify.com/CVE-2006-6308/index.md)
```

## Sources

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

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