# CVE-2008-2794: Privilege escalation in n/a

> Local attackers can exploit a GUI vulnerability in the Symantec Altiris Notification Server Agent to escalate privileges.

- **Severity:** Medium 6.8 (`AV:L/AC:L/Au:S/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:** 20 Jun 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xpvc-gvmh-mpmj

## What is CVE-2008-2794?

CVE-2008-2794 is a medium-severity vulnerability in n/a, published on 20 Jun 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in the GUI in Symantec Altiris Notification Server Agent 6.x before 6.0 SP3 R8 allows local users to gain privileges via unknown attack vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2008-2794?

It affects 1 product.


Products: Symantec Altiris Notification Server.

## How do I fix CVE-2008-2794?

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

## Is CVE-2008-2794 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-0716](https://insights.sbomify.com/CVE-2008-0716/): Privilege escalation in n/a (medium 6.8)
- [CVE-2009-3035](https://insights.sbomify.com/CVE-2009-3035/): Hardcoded credentials in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2794 and fix it if it is affected.

What it is: CVE-2008-2794 is a medium-severity vulnerability in n/a, published on 20 Jun 2008. 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-2008-2794 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-2008-2794/ (Markdown: https://insights.sbomify.com/CVE-2008-2794/index.md)
```

## Sources

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

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