# CVE-2008-1664: Denial of service in n/a

> Remote attackers can cause a denial of service in HP-UX via unspecified vectors in the libc library.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 8 Aug 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4987-c898-3w5h

## What is CVE-2008-1664?

CVE-2008-1664 is a high-severity denial of service vulnerability in Hp Hp-Ux, published on 8 Aug 2008. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in libc on HP HP-UX B.11.23 and B.11.31 allows remote attackers to cause a denial of service via unknown vectors.

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

It affects 1 product.


Products: Hp Hp-Ux.

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

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

## Is CVE-2008-1664 being exploited?

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

## Other vulnerabilities in Hp Hp-Ux

- [CVE-2008-1668](https://insights.sbomify.com/CVE-2008-1668/): Privilege escalation in n/a (critical 10.0)
- [CVE-2008-1662](https://insights.sbomify.com/CVE-2008-1662/): Missing authorization in n/a (critical 10.0)
- [CVE-2007-6425](https://insights.sbomify.com/CVE-2007-6425/): Denial of service in n/a (critical 10.0)
- [CVE-2007-6195](https://insights.sbomify.com/CVE-2007-6195/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-4241](https://insights.sbomify.com/CVE-2007-4241/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-1664 is a high-severity denial of service vulnerability in Hp Hp-Ux, published on 8 Aug 2008. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-1664 in the wild and no public exploit code.

Affected product: Hp Hp-Ux. 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-1664/ (Markdown: https://insights.sbomify.com/CVE-2008-1664/index.md)
```

## Sources

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

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