# CVE-2002-2405: Security feature bypass in n/a

> Remote attackers can bypass firewall restrictions to access unauthorized services when UserAuth is configured for HTTP proxying only.

- **Severity:** Medium 4.9 (`AV:N/AC:M/Au:S/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2007
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qx7c-rg3g-8mqh

## What is CVE-2002-2405?

CVE-2002-2405 is a medium-severity vulnerability in n/a, published on 1 Nov 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Check Point FireWall-1 4.1 and Next Generation (NG), with UserAuth configured to proxy HTTP traffic only, allows remote attackers to pass unauthorized HTTPS, FTP and possibly other traffic through the firewall.

Weakness: CWE-264

## Which versions are affected by CVE-2002-2405?

It affects 1 product.


Products: Checkpoint Firewall-1.

## How do I fix CVE-2002-2405?

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

## Is CVE-2002-2405 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0040](https://insights.sbomify.com/CVE-2004-0040/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0469](https://insights.sbomify.com/CVE-2004-0469/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0039](https://insights.sbomify.com/CVE-2004-0039/): Code injection in n/a (critical 10.0)
- [CVE-2004-2679](https://insights.sbomify.com/CVE-2004-2679/): Information disclosure in n/a (high 7.8)
- [CVE-2004-0699](https://insights.sbomify.com/CVE-2004-0699/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2405 and fix it if it is affected.

What it is: CVE-2002-2405 is a medium-severity vulnerability in n/a, published on 1 Nov 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-2405 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-2002-2405/ (Markdown: https://insights.sbomify.com/CVE-2002-2405/index.md)
```

## Sources

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

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