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

> Local users with webstar privileges can gain root access by placing a malicious library in the current working directory of Kerio WebSTAR servers.

- **Severity:** Medium 6.2 (`AV:L/AC:H/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:** 28 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-26qr-qf74-v2w4

## What is CVE-2006-6131?

CVE-2006-6131 is a medium-severity vulnerability in n/a, published on 28 Nov 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Untrusted search path vulnerability in (1) WSAdminServer and (2) WSWebServer in Kerio WebSTAR (4D WebSTAR Server Suite) 5.4.2 and earlier allows local users with webstar privileges to gain root privileges via a malicious libucache.dylib helper library in the current working directory.

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

It affects 1 product.


Products: Kerio Webstar.

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

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

## Is CVE-2006-6131 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6131 exists.

Public exploit code:

- Kerio WebSTAR 5.4.2 (OSX) - 'libucache.dylib' Local Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6131 is a medium-severity vulnerability in n/a, published on 28 Nov 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6131 exists.

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-6131/ (Markdown: https://insights.sbomify.com/CVE-2006-6131/index.md)
```

## Sources

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

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