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

> Local users can gain privileges and execute commands via specific firewall UI interactions, potentially affecting underlying Windows components.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Jul 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-26q6-82cc-w6fm

## What is CVE-2006-3697?

CVE-2006-3697 is a high-severity vulnerability in n/a, published on 19 Jul 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

Agnitum Outpost Firewall Pro 3.51.759.6511 (462), as used in (1) Lavasoft Personal Firewall 1.0.543.5722 (433) and (2) Novell BorderManager Novell Client Firewall 2.0, does not properly restrict user activities in application windows that run in a LocalSystem context, which allows local users to gain privileges and execute commands (a) via the "open folder" option when no instance of explorer.exe is running, possibly related to the ShellExecute API function; or (b) by overwriting a batch file through the "Save Configuration As" option. NOTE: this might be a vulnerability in Microsoft Windows and explorer.exe instead of the firewall.

Weakness: CWE-264

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

It affects 3 products.


Products: Agnitum Outpost Firewall, Lavasoft Lavasoft Personal Firewall, Novell Client Firewall.

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

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

## Is CVE-2006-3697 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-0333](https://insights.sbomify.com/CVE-2007-0333/): Path traversal in n/a (high 7.2)
- [CVE-2004-2472](https://insights.sbomify.com/CVE-2004-2472/): Denial of service in n/a (medium 5.0)
- [CVE-2007-3086](https://insights.sbomify.com/CVE-2007-3086/): Denial of service in n/a (medium 4.9)
- [CVE-2006-7160](https://insights.sbomify.com/CVE-2006-7160/): Denial of service in n/a (medium 4.9)
- [CVE-2006-5721](https://insights.sbomify.com/CVE-2006-5721/): Denial of service in n/a (medium 4.9)

## Fix prompt for AI coding agents

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

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

## Sources

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

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