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

> Attackers can cause a system panic in SCO Unixware via the IGMP driver, leading to denial of service.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hgwp-f5r4-hvm6

## What is CVE-2009-1552?

CVE-2009-1552 is a high-severity denial of service vulnerability in Sco Unixware, published on 6 May 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in the IGMP driver in SCO Unixware Release 7.1.4 Maintenance Pack 4 allows attackers to cause a denial of service (system panic) via unspecified vectors.

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

It affects 1 product.


Products: Sco Unixware.

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

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

## Is CVE-2009-1552 being exploited?

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

## Other vulnerabilities in Sco Unixware

- [CVE-2000-0348](https://insights.sbomify.com/CVE-2000-0348/): Privilege escalation in n/a (critical 10.0)
- [CVE-1999-0836](https://insights.sbomify.com/CVE-1999-0836/): Path traversal in n/a (critical 10.0)
- [CVE-2000-0003](https://insights.sbomify.com/CVE-2000-0003/): Memory corruption in n/a (critical 10.0)
- [CVE-2000-0026](https://insights.sbomify.com/CVE-2000-0026/): Memory corruption in n/a (critical 10.0)
- [CVE-2000-1014](https://insights.sbomify.com/CVE-2000-1014/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1552 is a high-severity denial of service vulnerability in Sco Unixware, published on 6 May 2009. 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-2009-1552 in the wild and no public exploit code.

Affected product: Sco Unixware. 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-1552/ (Markdown: https://insights.sbomify.com/CVE-2009-1552/index.md)
```

## Sources

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

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