# CVE-2008-4190: Path traversal in n/a

> Local attackers can overwrite arbitrary files and execute code via symlink attacks on temporary files in the IPSEC livetest tool.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** Yes
- **Published:** 24 Sep 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pqmw-hq69-w92w

## What is CVE-2008-4190?

CVE-2008-4190 is a medium-severity path traversal vulnerability in n/a, published on 24 Sep 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The IPSEC livetest tool in Openswan 2.4.12 and earlier, and 2.6.x through 2.6.16, allows local users to overwrite arbitrary files and execute arbitrary code via a symlink attack on the (1) ipseclive.conn and (2) ipsec.olts.remote.log temporary files.  NOTE: in many distributions and the upstream version, this tool has been disabled.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 2 products.


Products: Openswan Openswan, Xelerance Openswan.

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

Change a configuration setting.

## Is CVE-2008-4190 being exploited?

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

Public exploit code:

- Openswan 2.4.12/2.6.16 - Insecure Temp File Creation Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-0162](https://insights.sbomify.com/CVE-2005-0162/): Memory corruption in n/a (high 7.2)
- [CVE-2011-2147](https://insights.sbomify.com/CVE-2011-2147/): Missing authorization in n/a (low 3.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-4190 is a medium-severity path traversal vulnerability in n/a, published on 24 Sep 2008. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-4190 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-2008-4190/ (Markdown: https://insights.sbomify.com/CVE-2008-4190/index.md)
```

## Sources

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

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