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

> Authenticated Sun Ray administrators can gain root privileges via unspecified vectors in utconfig, requiring immediate patching.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7rrq-2cr9-55qv

## What is CVE-2008-2112?

CVE-2008-2112 is a high-severity vulnerability in n/a, published on 8 May 2008. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unspecified vulnerability in Sun Ray Kiosk Mode 4.0 allows local and remote authenticated Sun Ray administrators to gain root privileges via unknown vectors related to utconfig.

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

It affects 1 product.


Products: Sun Ray Server Software.

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

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

## Is CVE-2008-2112 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-4294](https://insights.sbomify.com/CVE-2009-4294/): Other in n/a (critical 10.0)
- [CVE-2009-4295](https://insights.sbomify.com/CVE-2009-4295/): Weak cryptography in n/a (high 7.8)
- [CVE-2007-6482](https://insights.sbomify.com/CVE-2007-6482/): Denial of service in n/a (high 7.8)
- [CVE-2008-5422](https://insights.sbomify.com/CVE-2008-5422/): Information disclosure in n/a (high 7.5)
- [CVE-2002-2036](https://insights.sbomify.com/CVE-2002-2036/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2112 is a high-severity vulnerability in n/a, published on 8 May 2008. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-2112 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-2112/ (Markdown: https://insights.sbomify.com/CVE-2008-2112/index.md)
```

## Sources

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

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