# CVE-2009-1423: Denial of service in n/a

> Remote attackers can cause a denial of service in HP ProCurve Threat Management Services zl Module via unspecified vectors.

- **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:** 14 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xm5h-4r7m-2g3m

## What is CVE-2009-1423?

CVE-2009-1423 is a high-severity denial of service vulnerability in n/a, published on 14 Jul 2009. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in HP ProCurve Threat Management Services zl Module (J9155A) ST.1.0.090213 and earlier allows remote attackers to cause a denial of service via unknown vectors, aka PR_39898, a different vulnerability than CVE-2009-1424 and CVE-2009-1425.

## Which versions are affected by CVE-2009-1423?

It affects 1 product.


Products: Hp Procurve Threat Management Services Zl Module.

## How do I fix CVE-2009-1423?

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

## Is CVE-2009-1423 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1422](https://insights.sbomify.com/CVE-2009-1422/): Privilege escalation in n/a (critical 10.0)
- [CVE-2009-1424](https://insights.sbomify.com/CVE-2009-1424/): Denial of service in n/a (high 7.8)
- [CVE-2009-1425](https://insights.sbomify.com/CVE-2009-1425/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1423 and fix it if it is affected.

What it is: CVE-2009-1423 is a high-severity denial of service vulnerability in n/a, published on 14 Jul 2009. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-1423 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-2009-1423/ (Markdown: https://insights.sbomify.com/CVE-2009-1423/index.md)
```

## Sources

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

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