# CVE-2007-5665: Privilege escalation in n/a

> Local attackers can escalate privileges by exploiting world-writable diagnostic script directories in Novell ZENworks Endpoint Security Management.

- **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:** 9 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3qvq-5r47-f846

## What is CVE-2007-5665?

CVE-2007-5665 is a high-severity vulnerability in n/a, published on 9 Jan 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

STEngine.exe 3.5.0.20 in Novell ZENworks Endpoint Security Management (ESM) 3.5, and other ESM versions before 3.5.0.82, dynamically creates scripts in a world-writable directory when generating diagnostic reports, which allows local users to gain privileges, as demonstrated by creating a cmd.exe binary in the diagnostic report directory.

Weakness: CWE-264

## Which versions are affected by CVE-2007-5665?

It affects 1 product.


Products: Novell Zenworks Endpoint Security Management.

## How do I fix CVE-2007-5665?

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

## Is CVE-2007-5665 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5665 and fix it if it is affected.

What it is: CVE-2007-5665 is a high-severity vulnerability in n/a, published on 9 Jan 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-2007-5665 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-2007-5665/ (Markdown: https://insights.sbomify.com/CVE-2007-5665/index.md)
```

## Sources

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

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