# CVE-2005-4093: Security feature bypass in n/a

> Remote attackers can bypass security policies by modifying the local policy file in Check Point VPN-1 SecureClient.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5qph-qc32-4f64

## What is CVE-2005-4093?

CVE-2005-4093 is a medium-severity vulnerability in n/a, published on 8 Dec 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Check Point VPN-1 SecureClient NG with Application Intelligence R56, NG FP1, 4.0, and 4.1 allows remote attackers to bypass security policies by modifying the local copy of the local.scv policy file after it has been downloaded from the VPN Endpoint.

Weakness: CWE-264

## Which versions are affected by CVE-2005-4093?

It affects 2 products.


Products: Checkpoint Secureclient Ng, Checkpoint Vpn-1 Secureclient.

## How do I fix CVE-2005-4093?

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

## Is CVE-2005-4093 being exploited?

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

Public exploit code:

- Check Point VPN-1 SecureClient 4.0 < 4.1 - Policy Bypass (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4093 and fix it if it is affected.

What it is: CVE-2005-4093 is a medium-severity vulnerability in n/a, published on 8 Dec 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-4093 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-2005-4093/ (Markdown: https://insights.sbomify.com/CVE-2005-4093/index.md)
```

## Sources

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

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