# CVE-2008-1397: Business logic in n/a

> Authenticated remote users can cause VPN tunnel outages and potentially intercept traffic by misconfiguring local IP addresses to match tunnel endpoints.

- **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:** 20 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rwxm-mv8x-336c

## What is CVE-2008-1397?

CVE-2008-1397 is a medium-severity vulnerability in n/a, published on 20 Mar 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Check Point VPN-1 Power/UTM, with NGX R60 through R65 and NG AI R55 software, allows remote authenticated users to cause a denial of service (site-to-site VPN tunnel outage), and possibly intercept network traffic, by configuring the local RFC1918 IP address to be the same as one of this tunnel's endpoint RFC1918 IP addresses, and then using SecuRemote to connect to a network interface at the other endpoint.

Weakness: CWE-264

## Which versions are affected by CVE-2008-1397?

It affects 5 products.


Products: Checkpoint Check Point Vpn-1 Pro, Checkpoint Vpn-1, Checkpoint Vpn-1 Firewall-1, Checkpoint Vpn-1 Power Utm, Checkpoint Vpn-1 Power Utm With Ngx.

## How do I fix CVE-2008-1397?

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

## Is CVE-2008-1397 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1397 and fix it if it is affected.

What it is: CVE-2008-1397 is a medium-severity vulnerability in n/a, published on 20 Mar 2008. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-1397 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-2008-1397/ (Markdown: https://insights.sbomify.com/CVE-2008-1397/index.md)
```

## Sources

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

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