# CVE-2005-0162: Memory corruption in n/a

> Remote authenticated attackers can execute arbitrary code via a stack-based buffer overflow in Openswan when XAUTH and PAM are enabled.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fg53-7fcw-mx53

## What is CVE-2005-0162?

CVE-2005-0162 is a high-severity memory corruption vulnerability in n/a, published on 29 Jan 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Stack-based buffer overflow in the get_internal_addresses function in the pluto application for Openswan 1.x before 1.0.9, and Openswan 2.x before 2.3.0, when compiled with XAUTH and PAM enabled, allows remote authenticated attackers to execute arbitrary code.

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

It affects 2 products.


Products: Openswan Openswan, Xelerance Openswan.

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

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

## Is CVE-2005-0162 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-4190](https://insights.sbomify.com/CVE-2008-4190/): Path traversal in n/a (medium 4.4)
- [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-2005-0162 and fix it if it is affected.

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

## Sources

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

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