# CVE-2008-0704: Auth bypass in n/a

> Remote attackers can obtain unspecified access to HP OpenVMS TCP/IP Services SSH server, requiring vendor patches.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j2vp-w8fr-w95m

## What is CVE-2008-0704?

CVE-2008-0704 is a critical authentication bypass vulnerability in n/a, published on 28 Mar 2008. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the SSH server in HP OpenVMS TCP/IP Services on OpenVMS on the Alpha platform with 5.4 before ECO 7, and on the Integrity and Alpha platforms with 5.5 before ECO 3 and 5.6 before ECO 2, allows remote attackers to obtain unspecified access via unknown vectors.

Weakness: CWE-264

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

It affects 1 product.


Products: Hp Open Vms Tcp-Ip Services.

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

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

## Is CVE-2008-0704 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2008-0704 is a critical authentication bypass vulnerability in n/a, published on 28 Mar 2008. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-0704 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-0704/ (Markdown: https://insights.sbomify.com/CVE-2008-0704/index.md)
```

## Sources

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

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