# CVE-2007-3795: Denial of service in n/a

> Attackers can cause a denial of service on HP-UX systems by sending malicious data to a specific port in Hitachi TP1/Server Base.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4xq7-8qg7-4xjf

## What is CVE-2007-3795?

CVE-2007-3795 is a high-severity denial of service vulnerability in n/a, published on 15 Jul 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in Hitachi TP1/Server Base before 03-05-/P, 05-00-x before 05-00-/G, 05-01-x before 05-01-/A, and 05-02-x before 05-02-/C on HP-UX 11.0 through 11i v3 allows attackers to cause a denial of service by sending certain data to a port.

## Which versions are affected by CVE-2007-3795?

It affects 1 product.


Products: Hitachi Tpi Server Base.

## How do I fix CVE-2007-3795?

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

## Is CVE-2007-3795 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3795 and fix it if it is affected.

What it is: CVE-2007-3795 is a high-severity denial of service vulnerability in n/a, published on 15 Jul 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-2007-3795 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-2007-3795/ (Markdown: https://insights.sbomify.com/CVE-2007-3795/index.md)
```

## Sources

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

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